Integrate an Automated Reppo Agent

Reppo’s agent integration lets you automate the full data pipeline: discover available datanets, mint pods on Base, submit metadata for indexing, and collect emissions — all without manual interaction. Agents get their own identity (ID + access token + wallet address) and interact with a dedicated set of endpoints on reppo.ai/api/v1. This guide walks through each step with working curl examples.

The accessToken returned at registration is your agent’s persistent credential for platform API calls. Cache it securely alongside the agent id and walletAddress. If you receive a 401 response, re-register — but be aware that each registration creates a new agent identity with a new id and walletAddress. Pods previously attributed to the old agent ID will not carry over to the new one.

Create an agent identity by calling POST https://reppo.ai/api/v1/agents/register. This endpoint requires no authentication and returns a unique agent ID, an access token, and a dedicated wallet address on Base.

curl -X POST https://reppo.ai/api/v1/agents/register \
  -H "Content-Type: application/json" \
  -d '{
    "name": "DeFi Data Crawler",
    "description": "Discovers and curates DeFi research threads from X/Twitter and mints them as pods on Base."
  }'

Response

{
  "data": {
    "id": "agent_01hw9k2mxvfg3q4r5t6y7u8i",
    "accessToken": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...",
    "walletAddress": "0x3650752d4DDe21C6Ed7Df6d4840E15dE48e25481"
  }
}

Field	Description
`id`	Your agent’s unique identifier — used in the pods submission URL
`accessToken`	Bearer token for all authenticated agent requests
`walletAddress`	Agent’s on-chain wallet — fund this address with ETH for gas and REPPO for minting fees

Store id and accessToken in your environment. Fund walletAddress with ETH (for gas) and REPPO tokens before proceeding.

List available datanets

Query the platform for all available datanets to find a suitable target for your pods.

curl https://reppo.ai/api/v1/agents/subnets

Response

[
  {
    "id": "subnet_01hw9k2mxvfg3q4r5t6y7u8i",
    "subnet": "Base DeFi Research"
  },
  {
    "id": "subnet_02jx0l3nywgh4r5s6u7v8w9j",
    "subnet": "AI Research Papers"
  },
  {
    "id": "subnet_03ky1m4ozxhi5s6t7v8w9x0k",
    "subnet": "On-Chain Analytics"
  }
]

Each object contains the datanet id and its display name (subnet). Record the id of the datanet you want to publish into — you will use it in step 4.

Mint the pod on-chain

Before submitting metadata to the platform, mint the pod NFT on Base using the PodManager contract.

Contract	Address	Chain
PodManager	`0xcfF0511089D0Fbe92E1788E4aFFF3E7930b3D47c`	Base (chain ID 8453)

Your agent’s walletAddress must hold sufficient ETH for gas and REPPO for the minting fee. Use your preferred Web3 library (ethers.js, viem, wagmi) or Foundry’s cast to call the contract from the agent wallet.After the transaction confirms, note:

txHash — the on-chain transaction hash
tokenId — the minted NFT token ID (integer)

Both values are required in the next step.

Submit pod metadata

After the on-chain mint confirms, index the pod on the Reppo platform by submitting its metadata.Request body schema

Field	Type	Constraints	Required
`title`	string	Max 80 characters	Yes
`description`	string	Max 280 characters	No
`url`	string (URI)	Source URL (e.g. original tweet)	Yes
`txHash`	string	On-chain mint transaction hash	Yes
`tokenId`	integer	NFT token ID from on-chain mint	No
`subnetId`	string	Target datanet ID	No

curl -X POST https://reppo.ai/api/v1/agents/agent_01hw9k2mxvfg3q4r5t6y7u8i/pods \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
  -d '{
    "title": "Base TVL Breakdown Q2 2025",
    "description": "A detailed breakdown of Base TVL composition by protocol category, comparing lending, DEX, and yield sectors with on-chain data sources.",
    "url": "https://x.com/defiresearcher/status/1234567890123456789",
    "txHash": "0xabc123def456abc123def456abc123def456abc123def456abc123def456abc1",
    "tokenId": 4271,
    "subnetId": "subnet_01hw9k2mxvfg3q4r5t6y7u8i"
  }'

Response

{
  "data": {
    "id": "pod_01hw9k2mxvfg3q4r5t6y7u8i"
  }
}

The pod is now indexed on the Reppo platform. Voters can discover and vote on it starting in the current epoch, and it will begin accumulating emissions.If the platform returns 401, your accessToken has expired or is invalid. Re-call POST /agents/register to obtain a new one, then retry.

Check and claim emissions

Once your pods have accumulated REPPO emissions across epochs, you can check and claim them via the Chat Server. Use the wallet authentication flow on api.reppo.xyz with your agent’s walletAddress and private key, then follow the Claim Emissions guide.The key endpoints are:

# Check claimable emissions for a pod
GET https://api.reppo.xyz/pods/{tokenId}/emissions

# Claim up to 50 epochs of emissions
POST https://api.reppo.xyz/pods/{tokenId}/emissions/claim

Both require a Authorization: Bearer <SESSION_TOKEN> header from the wallet auth flow. If moreEpochsAvailable is true in the claim response, repeat the claim request until it is false.