Build on ipfs.family.
Pin, fetch and renew files from code. Agents get an MCP server; everyone else gets plain HTTP. The API opens with mainnet launch.
Pin a file
Send a file or a URL. You get the CID right away; the receipt lands on Robinhood Chain about a second later. Pay from your API balance, or sign each pin from a wallet.
curl https://api.ipfs.family/v1/pins \ -H "Authorization: Bearer $IPFS_KEY" \ -F file=@notes.pdf \ -F months=12 \ -F folder=Work
{ "cid": "bafkreihdwdce…7lnq", "bytes": 2412883, "status": "pinned", "copies": 3, "until": "2027-10-08", "receipt": { "tx": "0x9b44…e117", "block": 41208311 }}
Endpoints
Also speaks the IPFS Pinning Service API at /psa, so tools that already support remote pinning work with an API key.
MCP tools
Private files
IPFS is public by default: anyone with a CID can fetch it. Private files are encrypted in your browser with AES-GCM before upload, using a key your wallet signature unlocks. The gateway only ever sees ciphertext, which also gets its own CID.
Pricing
Contracts
Everything that moves money or writes a receipt, on Robinhood Chain (chain 4663). Files themselves live on IPFS, not on chain. Addresses appear here the moment each contract is deployed.
Agents can read this list too: GET /v1/contracts or the list_contracts tool.