Cred Protocol

• Name: Cred Protocol
• URL: https://credprotocol.com/
• Category: onchain credit-intelligence middleware / DeFi underwriting-and-reputation control plane / agent trust-scoring API
• Tags: ethereum-ecosystem
• Summary: Cred Protocol is onchain credit-intelligence middleware. The useful surface is underwriting logic, multichain wallet scoring, pay-per-request auth, and agent-facing trust APIs — not another dashboard pretending to be a reputation layer.
• What it does:
  • Generates credit scores in a 300-1000 range for blockchain addresses based on onchain activity
  • Produces credit reports, enhanced reports, portfolio composition views, chain-specific summaries, and aggregated multi-address scoring endpoints
  • Aggregates wallet and protocol data across 10+ chains, with especially deep lending coverage on Ethereum and Base plus tracked positions in Aave and Compound
  • Incorporates identity and reputation signals such as ENS, Basename, Gitcoin Passport, POAPs, Goldfinch UID, and sybil-detection analysis
  • Supports both API-key authentication and x402 pay-per-request authentication with USDC on Base and SKALE, including no-account-required access
  • Exposes agent-facing surfaces including MCP services, SDKs, Express, Hono, Next.js, and FastAPI middleware, plus onchain agent-reputation endpoints and registries
• Key claims:
  • The homepage frames Cred Protocol around “Trust and transparency for agentic finance,” which is a clean signal that the product is being sold as trust infrastructure for autonomous financial workflows rather than as a generic analytics layer
  • The docs say Cred provides credit scoring and reporting APIs for blockchain addresses, with multi-chain aggregation, real-time scoring through the Andromeda model, identity verification, and developer sandbox and SDK workflows
  • The chains-and-protocols page shows Cred is scoring behavior, not just balances: lending and borrowing history across Aave and Compound, wallet composition, transaction activity, and reputation attestations all feed the output
  • The authentication guide documents x402 payment auth, 402 Payment Required flows, Base and SKALE support, and immediate request-level settlement semantics, which makes the product’s request-priced control surface unusually explicit
  • The docs-wide llms.txt index exposes a broader surface than a single score endpoint, including MCP services, agent feedback submission, sybil detection, middleware packages, SDKs, and capital-efficiency or undercollateralized-lending use cases
  • The same docs index exposes agent registry and reputation endpoints under an ERC-8004-oriented surface, reinforcing that Cred is pushing toward agentic reputation infrastructure in addition to borrower scoring
• Whitepaper: No canonical standalone Cred Protocol whitepaper or litepaper surfaced in this pass. The clearest current source of truth was the official site, the docs portal and llms.txt index, the chain-coverage and authentication guides, and the public GitHub organization; see ../whitepapers/cred-protocol-primary-sources-2026-05-03.md.
• Sources:
  • https://credprotocol.com/
  • https://docs.credprotocol.com/introduction
  • https://docs.credprotocol.com/chains-and-protocols
  • https://docs.credprotocol.com/guides/authentication
  • https://docs.credprotocol.com/llms.txt
  • https://github.com/credprotocol

Internal linkages

• Paid-request auth substrate: x402.
• Closest identity-and-attribute contrast from the current corpus: quadrata.

Control surface

• Practical authority sits in scoring-model definitions, supported-chain coverage, which identity and reputation inputs count, authentication and pricing policy, and the agent registry and trust endpoints built on top.

• The useful read is underwriting middleware with programmable trust outputs, not an abstract reputation badge.

• Last reviewed: 2026-06-16 UTC