Skip to main content
POST
/
api
/
v2
/
agents
/
{agent_id}
/
reputation
curl -X POST "https://api.credprotocol.com/api/v2/agents/18/reputation" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}'
{
  "submission_id": "550e8400-e29b-41d4-a716-446655440000",
  "agent_id": 18,
  "status": "pending",
  "estimated_completion_seconds": 45,
  "status_url": "/api/v2/agents/18/reputation/status/550e8400-e29b-41d4-a716-446655440000",
  "tags": ["creditScore", "sybilRisk", "identityCount"]
}

Documentation Index

Fetch the complete documentation index at: https://docs.credprotocol.com/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Computes Cred Protocol credit score, sybil risk, and identity attestations for the given agent, then submits the results as on-chain feedback to the ERC-8004 Reputation Registry on Base. The submission happens asynchronously — this endpoint returns immediately with a tracking ID. Use the status endpoint to poll for completion.
This endpoint costs 10 Cred Units per submission (covers computation + on-chain gas on Base).

Authentication

MethodHeaderCost
API TokenAuthorization: Bearer YOUR_API_KEY10 Cred Units
x402 PaymentX-PAYMENT: <signed_payment>$0.10 USDC

Path Parameters

agent_id
integer
required
ERC-8004 agent ID from the Identity Registry. Must be >= 1.

Request Body

address
string
required
Ethereum address to score for this agent (e.g., 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045)
tags
array
Which feedback types to submit. Defaults to all three if omitted.Options: creditScore, sybilRisk, identityCount

Feedback Tags

TagDescriptionValue Range
creditScoreAndromeda 1.0 credit score300–1000
sybilRiskSybil detection risk score0 (human) – 100 (bot)
identityCountNumber of verified identity attestations0+

Response

Returns HTTP 202 Accepted with a tracking ID.
submission_id
string
UUID tracking this submission
agent_id
integer
The ERC-8004 agent ID
status
string
Initial status (always pending)
estimated_completion_seconds
integer
Estimated time to on-chain confirmation (typically ~45 seconds)
status_url
string
Relative URL to poll for submission status
tags
array
Feedback types being submitted
curl -X POST "https://api.credprotocol.com/api/v2/agents/18/reputation" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"}'
{
  "submission_id": "550e8400-e29b-41d4-a716-446655440000",
  "agent_id": 18,
  "status": "pending",
  "estimated_completion_seconds": 45,
  "status_url": "/api/v2/agents/18/reputation/status/550e8400-e29b-41d4-a716-446655440000",
  "tags": ["creditScore", "sybilRisk", "identityCount"]
}

Submission Lifecycle

The submission progresses through these statuses:
StatusDescription
pendingSubmission received, queued for processing
scoringComputing credit score, sybil risk, and identity attestations
uploadingUploading feedback JSON to IPFS
submittingSending giveFeedback transaction to Base
confirmedTransaction confirmed on-chain
failedAn error occurred (check the error field)

Performance

  • Response Time: Immediate (HTTP 202)
  • End-to-End Completion: ~45 seconds (scoring + IPFS upload + on-chain confirmation)