Technical reference — Walcert
How to call the agent from another agent or HTTP client. No ops secrets — public surface only.
Base URL (API)
https://walcert.globalscoreagent.comGET / returns the bilingual agent card JSON (discovery). Not the GSA human dashboard.
Public endpoints
Paid certificates: `{type}` ∈ origins | activity | multichain | portfolio. Free preview: origins | activity only (Alchemy); multichain/portfolio → 403; rate limit 8 req/IP / 15 min → 429.
| Method | Path | Auth | Delivers |
|---|---|---|---|
| GET | / | None | Bilingual agent card JSON (ERC-8004 discovery) |
| GET | /agent-card.json | None | Concordium CIS-8004 Agent Card (External Agent #1686) |
| GET | /health | None | Liveness |
| GET | /v1/quota | None | Provider quota / status |
| POST | /v1/preview/{type} | None | Free preview (origins/activity); 403/429 per rules |
| POST | /v1/certificates/{type} | x402 | Full certificate + signature + on-chain (x402 Celo, Base, or BNB) |
| POST | /v1/verify | None | Verify by tx_hash (DB + Celo + EIP-712); no x402 |
| GET | /.well-known/ai-tool/walcert-{type}.json | None | ERC-8257 manifest (origins | activity | multichain | portfolio) |
Request body
Preview and certificates expect the same JSON:
{
"wallet_address": "0x..."
}Public verification (`POST /v1/verify`) — only the anchor tx_hash is required:
{
"tx_hash": "0x..."
}x402 payment flow
Full certificates use the x402 paywall at $0.05 USDC (exact scheme). The client picks the network in the 402: Celo, Base, or BNB.
- 1POST /v1/certificates/{type} without payment → 402 with options (accepts[0] Base / CDP; accepts[1] Celo; accepts[2] BNB eip155:56 Permit2 / Dexter).
- 2Client signs on one network (EIP-3009 on Celo/Base, or Permit2 on BNB) and retries with PAYMENT-SIGNATURE / X-PAYMENT.
- 3Agent verifies and settles via that network facilitator → 200 + certificate. The giveFeedback anchor remains on Celo. On BNB the JSON may include a certificate.receipt voucher for the soulbound NFT claim.
Preview (/v1/preview/{type}): origins/activity only, free, 8 req/IP / 15 min. Facilitators: api.x402.celo.org (Celo), CDP (Base), Dexter (BNB). A Celo settlement does not index CDP Bazaar. The NFT receipt does not replace the Celo anchor.
ERC-8257 tools
The four paid certificates are registered as tools in the Agent Tool Registry (ERC-8257) on Base and Ethereum. One tool per certificate; billing is x402 at the endpoint. No NFT / subscription predicates.
- Base (8453)
- toolId 485–488
- Ethereum (1)
- toolId 163–166
- walcert-originsBase 485 · Eth 163
- walcert-activityBase 486 · Eth 164
- walcert-multichainBase 487 · Eth 165
- walcert-portfolioBase 488 · Eth 166
Manifests: GET /.well-known/ai-tool/walcert-{origins|activity|multichain|portfolio}.json on the agent origin.
What the paid certificate includes
- •A–F grade and full bilingual texts (summary, strengths, concerns).
- •GSA brand field (provider) inside the certificate.
- •signature — EIP-712 signature over data_hash.
- •onchain — giveFeedback anchor on the Reputation Registry (Celo).
- •If paid on BNB: certificate.receipt (voucher) for claiming the soulbound NFT on BSC — not the certificate and does not replace the Celo anchor.
- •Verifiable afterwards via POST /v1/verify (tx_hash) or the GSA dashboard.
Technical documentation
Schemas, deploy, and scoring detail live in the agent repo — we do not duplicate them here.
- Agent README
- Concordium Agent Card (JSON)
- Concordium Agent Registry
- Virtuals ACP — Walcert listing
- Agent.family — Instant-buyable listing
- Agent City
- CDP Bazaar — agentic.market listing
- Aigora — Celo 9699 profile
- BNB x402 + NFT receipt docs (repo)
- NFT receipt contract (BscScan)
- ERC-8257 tools docs (repo)
- CDP Bazaar docs (repo)
- Concordium CIS-8004 docs (repo)
- Virtuals ACP docs (repo)
- Certificates (ES)
- Certificates (EN)
- JSON schemas
- Deployment guide
Ready to integrate
Start with GET / (agent card), a preview, or POST /v1/verify; for the full certificate follow the x402 flow.