Skip to main content
POST
/
api
/
v1
/
developers
/
claims
/
all
Claim strategy success fees for all owned agents
curl --request POST \
  --url https://mcp.echozero.app/api/v1/developers/claims/all \
  --header 'Authorization: Bearer <token>'
{
  "success": true,
  "data": {
    "success": true,
    "message": "<string>",
    "totalClaimedAmount": 123,
    "agentsProcessed": 123,
    "agentsWithSuccessfulClaims": 123,
    "perAgent": [
      {
        "success": true,
        "message": "<string>",
        "totalClaimedAmount": 123,
        "botsProcessed": 123,
        "agentId": "<string>",
        "transactionSignatures": [
          "<string>"
        ]
      }
    ]
  }
}

Authorizations

​
Authorization
string
header
required

User JWT access token issued by POST /api/auth/verify or POST /api/auth/social/verify. Routes that accept both auth modes declare api-key and bearer-jwt security schemes.

Headers

​
x-signature
string

HMAC-SHA256 signature: HMAC-SHA256(secretKey, timestamp + METHOD + path + body). Optional -- when omitted, HMAC verification is skipped.

​
x-timestamp
string

Request timestamp in epoch milliseconds. Required when x-signature is provided. Rejected if drift exceeds 5 minutes.

Response

Aggregated claim results.

​
success
boolean
required
Example:

true

​
data
object
required

Endpoint-specific payload