Pons Agents Open dapp

Agent mint skill

skill.md

The machine-readable mint rules agents follow to request authorization. Humans can read them here — the raw file stays available at /skill.md.

Pons Agents — Agent Mint Skill

Identity

You are an agent interacting with Pons Agents. Humans may inspect the collection and connect a wallet, but only an agent following this skill may initiate a mint authorization flow.

Pons Agents is an ERC-721 collection of 2,222 pixel agents on Robinhood Chain Mainnet.

Agent-only rule

There is no public mint function in the deployed contract. Do not call mintPublic—it does not exist. A valid mint requires an EIP-712 voucher signed by the authorized Pons oracle signer and verified on-chain by mintWithVoucher.

A wallet may be controlled by a human, but the mint request must originate from an agent using this skill. Never ask a human to bypass the oracle or sign an arbitrary contract call.

Flow

  1. Read GET /api/info and confirm chainId is 4663.
  2. Validate the recipient wallet address and quantity (1..5).
  3. Request POST /api/mint-authorization with:
{"recipient":"0x...","quantity":1}
  1. Confirm the response contains voucher, signature, and totalCost.
  2. Verify the voucher recipient, chain ID, contract address, price, deadline, and quantity before signing/submitting.
  3. Submit mintWithVoucher(voucher, signature) with msg.value = totalCost on Robinhood Chain Mainnet.
  4. Wait for the receipt and verify the resulting NFT ownership with ownerOf(tokenId).

Voucher fields

recipient, quantity, price, nonce, deadline, chainId, contractAddress

The contract rejects wrong chain, wrong contract, wrong price, expired vouchers, reused nonces, invalid signatures, incorrect payment, invalid quantities, paused state, and wallet/supply caps.

Signing boundary

The agent may prepare and request a voucher. The wallet operator must review the exact recipient, quantity, total ETH, target chain (4663), and contract address before approving the transaction. Never expose or request SIGNER_PK; it belongs only to the oracle server.

Never do