Agent API — tool reference
All 21 tools of the Polypad agent API, in one place. This page is generated from the same code the API serves, so it always matches what the server does. No signup, no API key, no approval — point your agent at the MCP endpoint and call these tools. Read tools only fetch data. Prepare tools return an unsigned transaction, a plain summary, and a signing link — nothing moves without a signature, and Polypad never holds your keys.
Examples use public placeholder addresses: a real token (Agent Swarm) and a real tokenized fund (the Polyfund) where an address is needed, and 0x1111…1111 where your own wallet address goes. Replace the from address with the wallet that will sign. Amounts are decimal strings in base units (wei for ETH). Full rules — rate limits, error codes, versioning — are on the rules of the road page. How a prepared action goes from the agent to a signature to a confirmed result — and back to the agent — is on the sign loop page. Contracts are unaudited.
Read
polypad_what_can_i_do
Read — no signature neededWhat can I do
Start here. Explains what Polypad on Robinhood Chain can do from chat, example requests, live counts, how signing works, and the guardrails.
GET /api/agents/v2/onboard
Example — REST
curl "https://polypad.family/api/agents/v2/onboard"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_what_can_i_do","arguments":{}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
polypad_intent
Read — no signature neededUnderstand a request
Turns a plain-language request ("buy 0.01 ETH of POLYCAT", "launch a fund with POLYDASH") into the right tool call. Runs read-only requests directly. For actions that move funds it needs the wallet address in `from`; if details are missing it returns the questions to ask.
POST /api/agents/v2/intent
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/intent" -H "content-type: application/json" -d '{"text":"What tokens launched today?"}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_intent","arguments":{"text":"What tokens launched today?"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_token (409) — More than one token matches. Use the token address.
- ambiguous_fund (409) — More than one tokenized fund matches. Use the fund address.
polypad_token_protections
Read — no signature neededToken protections in plain words
A plain-language read of a token's on-chain protections: liquidity, fees, creator holdings, staking pool, vesting lock, bond. It says what is met, what is not, and what it cannot tell you. Not a promise about price.
GET /api/agents/v2/protections
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/protections?token=0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_token_protections","arguments":{"token":"0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_token (409) — More than one token matches. Use the token address.
polypad_portfolio
Read — no signature neededWallet portfolio (read-only)
Read-only view of a wallet: ETH, launch tokens with current exit value, fund shares with net value, and NFTs. Results are in ETH units from on-chain data. No USD value, no forecasts.
GET /api/agents/v2/portfolio
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/portfolio?address=0x1111111111111111111111111111111111111111"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_portfolio","arguments":{"address":"0x1111111111111111111111111111111111111111"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
polypad_get_tx_status
Read — no signature neededTransaction status
Follow up on a transaction: pending, confirmed, or failed, with a plain result (tokens bought, fund created, and so on) and an explorer link.
GET /api/agents/v2/tx/status
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/tx/status?hash=0x2a4c03794a3195f7a56120f488978d7d6f3a15e8ced3c964d8d55438f65704be"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_get_tx_status","arguments":{"hash":"0x2a4c03794a3195f7a56120f488978d7d6f3a15e8ced3c964d8d55438f65704be"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- tx_not_found (404) — No transaction with that hash on Robinhood Chain yet — it may not have been sent.
polypad_stats
Read — no signature neededAgent traffic stats
Counts of actions prepared through the agent API by action and ref tag. Per server process; the on-chain attribution suffix is the durable record.
GET /api/agents/v2/stats
Example — REST
curl "https://polypad.family/api/agents/v2/stats"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_stats","arguments":{}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
Trade
polypad_quote_trade
Read — no signature neededQuote a buy or sell
Quote a buy (ETH in) or sell (token amount in) for a launch token, on the bonding curve or in the Uniswap V4 pool after graduation. Returns expected output, minimum after slippage, and fees. A reading, not a promise.
GET /api/agents/v2/quote
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/quote?token=0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B&side=buy"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_quote_trade","arguments":{"token":"0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B","side":"buy"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_token (409) — More than one token matches. Use the token address.
- quote_failed (422) — The pool could not quote that amount. Try a smaller amount.
- not_tradable (409) — The token is in a phase that cannot be traded right now.
polypad_prepare_buy
Prepare — returns an unsigned transactionPrepare a buy
Prepares a buy of a launch token with ETH. Simulates it on-chain before returning. Returns the unsigned transaction (to, data, value, chainId 4663, gas estimate), a plain summary, and a one-tap signing link. Show the summary before the link. Never signs.
POST /api/agents/v2/prepare/buy
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/prepare/buy" -H "content-type: application/json" -d '{"token":"0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B","from":"0x1111111111111111111111111111111111111111"}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_prepare_buy","arguments":{"token":"0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B","from":"0x1111111111111111111111111111111111111111"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_token (409) — More than one token matches. Use the token address.
- amount_too_large (400) — One action is above the 25 ETH cap. Split it into smaller actions.
- confirm_large_required (400) — The amount is above 1 ETH. Confirm it with the user first, then resend with "confirmLarge": true.
- insufficient_balance (409) — The wallet holds less than the amount requested.
- simulation_reverted (422) — The on-chain simulation reverted — the transaction as built would fail. Nothing was sent.
- not_tradable (409) — The token is in a phase that cannot be traded right now.
- amount_exceeds_curve (409) — More tokens than the bonding curve can buy back right now. Try a smaller amount.
- payload_too_large (413) — Request body over 16 KB.
- key_material_rejected (400) — The request contained a private key or seed phrase. Never send one — Polypad never needs it. Nothing was processed.
polypad_prepare_sell
Prepare — returns an unsigned transactionPrepare a sell
Prepares a sale of a launch token for ETH, with the exact-amount approval step if needed. Simulates step 1 on-chain. Returns unsigned transactions, a summary, and a signing link. Accepts an amount or a percent of the wallet balance.
POST /api/agents/v2/prepare/sell
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/prepare/sell" -H "content-type: application/json" -d '{"token":"0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B","from":"0x1111111111111111111111111111111111111111"}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_prepare_sell","arguments":{"token":"0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B","from":"0x1111111111111111111111111111111111111111"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_token (409) — More than one token matches. Use the token address.
- amount_too_large (400) — One action is above the 25 ETH cap. Split it into smaller actions.
- confirm_large_required (400) — The amount is above 1 ETH. Confirm it with the user first, then resend with "confirmLarge": true.
- insufficient_balance (409) — The wallet holds less than the amount requested.
- simulation_reverted (422) — The on-chain simulation reverted — the transaction as built would fail. Nothing was sent.
- not_tradable (409) — The token is in a phase that cannot be traded right now.
- payload_too_large (413) — Request body over 16 KB.
- key_material_rejected (400) — The request contained a private key or seed phrase. Never send one — Polypad never needs it. Nothing was processed.
Launch
polypad_list_tokens
Read — no signature neededBrowse tokens
Trending, new, graduating, or high-volume token launches on Polypad, with search. Counts activity from on-chain trades. No price predictions.
GET /api/agents/v2/tokens
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/tokens"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_list_tokens","arguments":{}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
polypad_get_token
Read — no signature neededToken details
One token: price reading, bonding-curve progress, creator, fees, and links. Accepts a symbol, name, token address, or launch address.
GET /api/agents/v2/token
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/token?token=0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_get_token","arguments":{"token":"0x3Da9244DDE38284017fD15e45d1Fdf66D3617B4B"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_token (409) — More than one token matches. Use the token address.
polypad_prepare_token_launch
Prepare — returns an unsigned transactionPrepare a token launch
Prepares launching a new token on the Polypad factory, with the Agent-launched label by default. Validates every field, simulates createLaunch, and returns the unsigned transaction, a summary, and a signing link.
POST /api/agents/v2/prepare/token-launch
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/prepare/token-launch" -H "content-type: application/json" -d '{"from":"0x1111111111111111111111111111111111111111","name":"Example Token","symbol":"EXMPL","creatorFeeBps":100}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_prepare_token_launch","arguments":{"from":"0x1111111111111111111111111111111111111111","name":"Example Token","symbol":"EXMPL","creatorFeeBps":100}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- amount_too_large (400) — One action is above the 25 ETH cap. Split it into smaller actions.
- confirm_large_required (400) — The amount is above 1 ETH. Confirm it with the user first, then resend with "confirmLarge": true.
- simulation_reverted (422) — The on-chain simulation reverted — the transaction as built would fail. Nothing was sent.
- payload_too_large (413) — Request body over 16 KB.
- key_material_rejected (400) — The request contained a private key or seed phrase. Never send one — Polypad never needs it. Nothing was processed.
Tokenized Funds
polypad_list_fund_templates
Read — no signature neededFund templates
The published strategy templates a fund can be created from: allowed assets, position and trade caps, performance fee, drawdown brake, and manager lock.
GET /api/agents/v2/fund-templates
Example — REST
curl "https://polypad.family/api/agents/v2/fund-templates"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_list_fund_templates","arguments":{}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
polypad_list_funds
Read — no signature neededDiscover funds
Polypad Funds with filters: open for minting, status, template, asset held, manager, factory, search, and sort by newest, raise progress, deadline, or shares.
GET /api/agents/v2/funds
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/funds"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_list_funds","arguments":{}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
polypad_get_fund
Read — no signature neededFund details
One fund: status, raise progress, price per share, fees, assets, template rules, and whether public minting is open.
GET /api/agents/v2/fund
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/fund?fund=0x7c1d31629ac68aebe83f230edbc7eacfc26285ef"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_get_fund","arguments":{"fund":"0x7c1d31629ac68aebe83f230edbc7eacfc26285ef"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_fund (409) — More than one tokenized fund matches. Use the fund address.
polypad_prepare_fund_create
Prepare — returns an unsigned transactionPrepare a fund launch
Prepares creating a fund from a published template (Phase 6 factory by default). Give templateId, or list the assets wanted and it matches a template, or tells you honestly that none can hold them. Returns the unsigned createFund transaction, what the manager must mint next, and a signing link.
POST /api/agents/v2/prepare/fund-create
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/prepare/fund-create" -H "content-type: application/json" -d '{"from":"0x1111111111111111111111111111111111111111","name":"Example Token","symbol":"EXMPL"}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_prepare_fund_create","arguments":{"from":"0x1111111111111111111111111111111111111111","name":"Example Token","symbol":"EXMPL"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- unknown_template (404) — No Strategy with that id. List the strategies first.
- no_matching_template (422) — No Strategy can hold the requested assets.
- choose_template (409) — More than one Strategy fits the assets. Ask the user which one.
- amount_too_large (400) — One action is above the 25 ETH cap. Split it into smaller actions.
- confirm_large_required (400) — The amount is above 1 ETH. Confirm it with the user first, then resend with "confirmLarge": true.
- simulation_reverted (422) — The on-chain simulation reverted — the transaction as built would fail. Nothing was sent.
- payload_too_large (413) — Request body over 16 KB.
- key_material_rejected (400) — The request contained a private key or seed phrase. Never send one — Polypad never needs it. Nothing was processed.
polypad_prepare_fund_mint
Prepare — returns an unsigned transactionPrepare a fund investment
Prepares minting shares of an open fund. Checks the raise is open, that public minting is open (the manager has to mint the required shares before anyone else), supply, and balance. Simulates, then returns unsigned transactions, a summary, and a signing link.
POST /api/agents/v2/prepare/fund-mint
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/prepare/fund-mint" -H "content-type: application/json" -d '{"from":"0x1111111111111111111111111111111111111111","fund":"0x7c1d31629ac68aebe83f230edbc7eacfc26285ef"}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_prepare_fund_mint","arguments":{"from":"0x1111111111111111111111111111111111111111","fund":"0x7c1d31629ac68aebe83f230edbc7eacfc26285ef"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_fund (409) — More than one tokenized fund matches. Use the fund address.
- amount_too_large (400) — One action is above the 25 ETH cap. Split it into smaller actions.
- confirm_large_required (400) — The amount is above 1 ETH. Confirm it with the user first, then resend with "confirmLarge": true.
- insufficient_balance (409) — The wallet holds less than the amount requested.
- simulation_reverted (422) — The on-chain simulation reverted — the transaction as built would fail. Nothing was sent.
- raise_closed (409) — The tokenized fund is not open for minting.
- sold_out (409) — Sold out (NFT collection, or no shares left).
- skin_required (409) — Public minting is not open yet — the manager must mint their required shares first.
- payload_too_large (413) — Request body over 16 KB.
- key_material_rejected (400) — The request contained a private key or seed phrase. Never send one — Polypad never needs it. Nothing was processed.
polypad_prepare_fund_redeem
Prepare — returns an unsigned transactionPrepare a fund exit or refund
Prepares exiting a fund after its raise closes (pro-rata share of the vault) or a refund if the raise failed. Finds the wallet's shares on-chain, or takes a quantity or specific ids.
POST /api/agents/v2/prepare/fund-redeem
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/prepare/fund-redeem" -H "content-type: application/json" -d '{"from":"0x1111111111111111111111111111111111111111","fund":"0x7c1d31629ac68aebe83f230edbc7eacfc26285ef"}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_prepare_fund_redeem","arguments":{"from":"0x1111111111111111111111111111111111111111","fund":"0x7c1d31629ac68aebe83f230edbc7eacfc26285ef"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_fund (409) — More than one tokenized fund matches. Use the fund address.
- simulation_reverted (422) — The on-chain simulation reverted — the transaction as built would fail. Nothing was sent.
- raise_open (409) — The tokenized fund is still raising. Exit opens after the raise closes; a refund opens only if the raise fails.
- no_shares (409) — The wallet holds no shares of that tokenized fund.
- not_holder (409) — The wallet does not hold the share(s) being redeemed.
- unsupported_fund (409) — Exits from this fund type are not prepared by the API yet. Open the fund page.
- payload_too_large (413) — Request body over 16 KB.
- key_material_rejected (400) — The request contained a private key or seed phrase. Never send one — Polypad never needs it. Nothing was processed.
NFTs
polypad_list_nfts
Read — no signature neededBrowse NFT collections
Polypad NFT collections with status (commitment window, public mint, sold out), price, supply, and royalties.
GET /api/agents/v2/nfts
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/nfts"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_list_nfts","arguments":{}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
polypad_list_nft_listings
Read — no signature neededBrowse marketplace listings
Active fixed-price NFT listings on the Polypad marketplace, lowest price at the top, optionally for one collection or under a price.
GET /api/agents/v2/nfts/listings
Inputs
Example — REST
curl "https://polypad.family/api/agents/v2/nfts/listings"
Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_list_nft_listings","arguments":{}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
polypad_prepare_nft_buy
Prepare — returns an unsigned transactionPrepare an NFT buy or mint
Prepares either a marketplace purchase (listingId) or a public mint from a fixed-price collection (collection + quantity). Checks supply, wallet limits, and price, then simulates. Returns unsigned transactions, a summary, and a signing link. Collections still in their commitment window are sent to the collection page instead.
POST /api/agents/v2/prepare/nft-buy
Inputs
Example — REST
curl -X POST "https://polypad.family/api/agents/v2/prepare/nft-buy" -H "content-type: application/json" -d '{"from":"0x1111111111111111111111111111111111111111"}'Example — MCP
curl -X POST "https://polypad.family/api/mcp" -H "content-type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"polypad_prepare_nft_buy","arguments":{"from":"0x1111111111111111111111111111111111111111"}}}'What can go wrong
- invalid_params (400) — A field was missing, the wrong type, or out of range (bad address, bad number, bad hash). The error names the field.
- invalid_api_key (401) — The API key sent was unknown or revoked. Free calls need no key — send no key at all, or get a Pro key from /agents/accounts.
- rate_limited (429) — Too many requests from this IP. Wait a minute; the reply says how long (retry-after).
- rpc_unavailable (503) — The chain data source could not be reached. Retry shortly.
- internal_error (500) — Unexpected error. Nothing was signed or sent.
- not_found (404) — No token, tokenized fund, collection, listing, or endpoint matched.
- ambiguous_collection (409) — More than one collection matches. Use the collection address.
- amount_too_large (400) — One action is above the 25 ETH cap. Split it into smaller actions.
- confirm_large_required (400) — The amount is above 1 ETH. Confirm it with the user first, then resend with "confirmLarge": true.
- insufficient_balance (409) — The wallet holds less than the amount requested.
- simulation_reverted (422) — The on-chain simulation reverted — the transaction as built would fail. Nothing was sent.
- sold_out (409) — Sold out (NFT collection, or no shares left).
- commit_window_open (409) — The collection is still in its commitment window. Commit from the collection page.
- wallet_cap (409) — The collection’s per-wallet mint limit is reached.
- listing_not_valid (409) — The listing is sold, cancelled, expired, or no longer backed by the seller.
- own_listing (409) — This wallet is the seller of that listing.
- unsupported_collection_type (501) — Buys from bonding-curve collections are not prepared by the API yet. Open the collection page.
- payload_too_large (413) — Request body over 16 KB.
- key_material_rejected (400) — The request contained a private key or seed phrase. Never send one — Polypad never needs it. Nothing was processed.