Round 1 against STRATEGY-2026-10-23.md's backlog: - Wire register_agent/stake/set_credit_score/deposit_liquidity to the real Casper Testnet contracts (lib/casper/live_bridge.ts), verified live against the real RPC node with a freshly generated (unfunded) keypair (npm run casper:keygen). Honesty flags built in for the Odra payable calling convention and the admin-gated set_credit_score call. - Unblock NEAR's paid x402 route (npm run near:keygen generates a real implicit account id); QIE stays correctly flagged as blocked on unconfirmed external facts (asset contract, facilitator), not env plumbing. - New public Home tab: live-stats hero, how-it-works, a real competitor comparison table, and a "90-second proof" that calls the real API live in the browser (verified end-to-end with gstack browse). - Cold-start UX: visible retry state in X402Playground + the TS SDK, plus a keep-warm self-ping (lib/services/keepalive.ts) so the free Render dyno rarely idles out from under a real first-time caller. - New GET /v1/credit-score/:agentId alias + docs/integrations/ samples for Skyfire/Nevermined/Coinbase x402. - Self-hosting quickstart: root docker-compose.yml + scripts/bootstrap.sh, both run for real; fixed a real EACCES crash-loop bug in infra/Dockerfile (non-root user never owned the /data volume mount) found while verifying. 450/450 tests pass, typecheck clean, frontend build clean.
Integrating cred402 on top of your payment rail
STRATEGY-2026-10-23.md's §2 "layer axis" move: Skyfire, Nevermined and Coinbase's own x402 reference stack are payment rails, not underwriting. They answer "can this agent pay me right now?" — not "should I extend this agent credit, and how much?" cred402 answers the second question, and it does not care which rail you used to answer the first.
Every sample in this directory calls the same real, live endpoint:
GET /v1/credit-score/:agentId
- No x402 payment required — it is a normal scoped/rate-limited
v1REST GET, authenticated the same way as every otherv1route (optionalAuthorization: Bearer <key>orX-API-Key: <key>; anonymous callers get the default public rate limit, a key gets a higher one — seePOST /v1/admin/api-keys). - Returns
lib/services/RiskPolicyManager's real credit score, PD, risk band, eligibility, reason codes and verified x402 revenue for any agent already known to cred402 — the identical logic the chain-specific paid routes serve (GET /v1/x402/credit-score/:idfor Algorand,GET /v1/x402/qie/credit-score/:id,GET /v1/x402/near/credit-score/:id), just without a second payment hop for an integrator who already bills their own callers. - Returns a real
404 agent_not_foundfor an agent cred402 has never seen — it never fabricates a score for an unknown identity.
If you want cred402 itself to be the payment-metered boundary (0.01
USDC/lookup, no monthly minimum — see /pricing.html), use the chain-
specific paid routes instead; those are documented in docs/algorand_x402.md,
docs/qie_x402.md, docs/near_x402.md.
Per-rail samples
skyfire.md— gate a Skyfire KYA-authenticated agent call behind a cred402 credit check before fulfilling it.nevermined.md— underwrite before settling a Nevermined-metered agent-to-agent payment.coinbase-x402.md— the "sits on top of x402" pattern for any agent already using the open x402 standard directly (Coinbase's reference facilitator or any other).
Each sample is a complete, runnable snippet — not pseudocode — against a
local npm run dev instance (http://localhost:4021) or the hosted
reference deployment (https://cred402-1.onrender.com).