# Kaderos A2A Revenue Router Listing Pack

## One-line Description

Kaderos adds payments, payment-gated execution, and receipts to A2A and MCP agents.

## Short Description

Kaderos is a local-first revenue router for agent builders. Agents can submit A2A tasks, receive Stripe payment links, wait for payment confirmation, execute through a protected local executor, and return public receipts.

## Long Description

Kaderos helps agent builders monetize agent capabilities without turning every agent into a billing, deployment, and compliance system. It exposes A2A, MCP discovery, OpenAPI, llms.txt, and public receipt endpoints. A protected local executor handles paid execution, Vercel deployment, Stripe payment links, Supabase queue state, and receipt logging.

Use Kaderos when an agent can perform valuable work but still needs a reliable way to package the work as a paid offer, request payment, execute only after payment, and give the buyer a receipt.

## Primary URLs

- Website: https://kaderos.io
- Docs: https://kaderos.io/docs
- Discovery page: https://kaderos.io/discovery
- Agent Card: https://kaderos.io/.well-known/agent-card.json
- A2A agent.json alias: https://kaderos.io/.well-known/agent.json
- MCP manifest: https://kaderos.io/mcp
- MCP server: https://kaderos.io/mcp-server/server.mjs
- OpenAPI: https://kaderos.io/openapi.json
- llms.txt: https://kaderos.io/llms.txt

## Tags

agent-to-agent, A2A, MCP, agent commerce, AI agents, payments, Stripe, execution receipts, local executor, revenue automation

## Target Users

- Agent builders who need monetization rails.
- MCP server owners who want paid execution.
- A2A-compatible platforms looking for commerce infrastructure.
- AI automation agencies packaging agent work for clients.

## Suggested Directory Submission

Title: Kaderos A2A Revenue Router

Tagline: Add payments and receipts to your agent in 15 minutes.

Category: Agent Commerce / MCP Tools / A2A Infrastructure

Description: Kaderos gives agents a revenue layer: A2A queue intake, Stripe payment links, payment-gated execution, Vercel deployment, Supabase-backed state, MCP tooling, and public receipts.

Install URL: https://kaderos.io/docs

Source/Server URL: https://kaderos.io/mcp-server/server.mjs

Discovery URL: https://kaderos.io/.well-known/agent-card.json

A2A well-known URL: https://kaderos.io/.well-known/agent.json

## Example Social Post

Agents can do valuable work, but most cannot charge, wait for payment, execute safely, and produce a receipt.

Kaderos adds that revenue layer:
- A2A queue intake
- Stripe payment links
- protected local execution
- public receipts
- MCP tools for agent clients

Docs: https://kaderos.io/docs

## Example Community Post

I built Kaderos as a local-first revenue router for A2A/MCP agents.

The core idea: if an agent can perform a valuable task, it should be able to hand off monetization to an infrastructure layer instead of reinventing payments, queue state, execution approvals, deployment, and receipts.

Current flow:
1. Agent submits an A2A task.
2. Kaderos stores it in a Supabase-backed queue.
3. The executor creates a Stripe payment link.
4. Stripe webhook marks the task as paid.
5. The local executor runs the task.
6. Kaderos publishes a receipt.

Docs and MCP install: https://kaderos.io/docs

## FAQ

### What is Kaderos?

Kaderos is an A2A revenue router for AI agents. It connects agent task intake with payments, execution gating, deployment, and receipts.

### Is Kaderos a hosted agent?

No. Kaderos is local-first. The public site exposes discovery and queue endpoints, while the protected executor runs locally.

### Does Kaderos execute before payment?

The intended production flow is payment-gated: a task is queued, a payment link is created, the webhook confirms payment, and then the local executor runs.

### What protocols does Kaderos expose?

Kaderos exposes A2A-style JSON-RPC, an Agent Card, MCP discovery, an installable stdio MCP server, OpenAPI, llms.txt, and receipt URLs.