Cred Protocol

@FloeLabs Congrats on the launch! Small typo on the url, we're at credprotocol.com cc @cred_protocol

Agents assessing agents, with results stored immutably on Base. That's the trust layer the agent economy needs. Full blog post → credprotocol.com/blog/mcp-servi… Docs → docs.credprotocol.com/mcp-services/o… @anthropic @CoinbaseDev #MCP #ERC8004

Setup is one JSON block: { "mcpServers": { "cred-protocol": { "type": "url", "url": "api.credprotocol.com/mcp" } } } Then ask your agent: "What's the reputation of vitalik.eth?" It figures out the rest — which tools to call, how to interpret the results, what to flag.

We just shipped 21 MCP tools that give any AI agent instant access to on-chain reputation intelligence. Identity verification. Sybil detection. Agent-to-agent trust scoring. Financial profiling. All live, all real blockchain data. Connect in 2 minutes from Claude Code, Cursor, or Claude Desktop. 🧵

The full breakdown - how Stripe MPP crypto deposits work, a side-by-side comparison of all three payment paths, and what this means for agents building on paid APIs: credprotocol.com/blog/stripe-mp…

Stripe is now processing machine payments on both sides: ◾ x402 — merchant settlement for API providers ◾ MPP — crypto deposits on Tempo One dashboard for all machine payment revenue, regardless of protocol. The settlement layer for the machine economy is taking shape.

Stripe now settles MPP payments on Tempo. We just added Stripe crypto deposits as a third payment rail for Cred Protocol's credit scoring API. An agent sends $0.01 USDC to a Stripe deposit address on Tempo → Stripe confirms → credit score delivered. No API key. No account. Just a wallet. 🧵👇

It's live right now. Try it: tempo request -X GET "api.credprotocol.com/api/v2/score/a…" Accepts Tempo payments, Cred credit, x402, and traditional API keys. Full MPP spec compliance. 🔗 credprotocol.com 📄 docs.credprotocol.com ⚙️ mpp.dev

Reputation has teeth. Credit decisions are tied to ERC-8004 identity tokens. Every repayment and every default flows back on-chain. Default on a credit line? It tanks your Cred Score and locks you out of future credit across ANY service that checks it. Good actors build trust portably. Bad actors get priced out.

💸 tempo (direct pay) — any agent with a @tempo wallet pays $0.01 USDC per request. No account, no API key. 🏦 cred (pay on credit) — Cred Score ≥ 640? Transact on credit, no upfront payment. We check on-chain reputation and extend credit. Machines with good history pay later.

Cred Protocol is a reputation layer for autonomous agents. Your wallet's borrowing history, repayment behavior, and protocol interactions become a portable credit score any counterparty can query in real time. We wired it into the Machine Payments Protocol (MPP) with two modes 👇

🧵 We just shipped something at the Tempo hackathon that we've been thinking about for a while: Agentic reputation. AI agents are about to transact at scale. But right now every API call is prepaid — no identity, no history, no trust. Every agent starts at zero, every time.

Great hackathon today, playing with the another piece of the agentic finance puzzle -> ⁦@tempo⁩ from @paradigm and ⁦@stripe⁩

Stripe validating x402 tells the market this isn't experimental anymore. Machine-to-machine payments are becoming standard internet infrastructure. We wrote the full breakdown — including our x402 endpoint architecture and what we're shipping next → credprotocol.com/blog/stripe-x4…

Agents aren't just consuming credit data — they're building services on top of it. Imagine an agent that sells counterparty risk assessments. It pulls credit scores + identity data + reputation signals, packages them, and charges a margin. Every transaction settled via x402 micropayment. Fully autonomous. What's the first x402 service you'd want an agent to pay for?

Stripe just added x402 payments. AI agents can now pay for APIs autonomously — no accounts, no keys, just USDC and an HTTP request. The machine economy just got its Stripe moment. 🧵