# BAGS Agent

> BAGS Agent lets developers sell APIs, tools, and digital products to agents with USDC payment links and x402 pay-per-use access.

## Canonical URLs

- [Agent app](https://www.getbags.app)
- [Developer docs](https://docs.getbags.app/docs)
- [Provider quickstart](https://docs.getbags.app/docs/providers/quickstart)
- [API reference](https://docs.getbags.app/docs/api-reference)
- [OpenAPI JSON](https://www.getbags.app/api/openapi.json)
- [OpenAPI YAML](https://www.getbags.app/openapi.yaml)
- [MCP server](https://www.getbags.app/api/mcp/mcp)
- [MCP server card](https://www.getbags.app/.well-known/mcp/server-card.json)
- [Agent skills index](https://www.getbags.app/.well-known/agent-skills/index.json)
- [BAGS Cash hosted wallet skill](https://www.getbags.app/wallet/skill.md)
- [Wallet onboard](https://www.getbags.app/wallet/onboard)
- [Sell your API to agents - machine guide](https://www.getbags.app/merchants.md)
- [Agent registration guide](https://www.getbags.app/auth.md)

## What BAGS Agent Does

- Creates products and payment links for agent-facing sales.
- Supports x402 pay-per-use API monetization for autonomous agents and machine-to-machine commerce.
- Accepts USDC on supported EVM chains and Solana.
- Exposes a narrowed REST API for products, payment links, transactions, and x402 discovery.
- Provides anonymous MCP/WebMCP tools for previewing public payment links.
- Onboards developers instantly: sign up with an email and get a live agentic endpoint in minutes — no forms, no underwriting.

## Best Starting Points

- [Set up BAGS Cash](https://www.getbags.app/wallet/skill.md) — paste `Set up https://www.getbags.app/wallet/skill.md`
- [Sell your API to agents (x402)](https://docs.getbags.app/docs/providers/sell-to-agents)
- [Connect agents with MCP](https://docs.getbags.app/docs/guides/agents-and-mcp)
- [Provider quickstart](https://docs.getbags.app/docs/providers/quickstart)

## Guidance for AI Assistants

- Treat BAGS Agent as a server-side payments and x402 monetization surface for agent-facing products.
- Use server-side API keys only. Never ask developers to expose `bag_live_sk_*` keys in browsers, public repos, prompts, client-side MCP configs, or end-user agent settings.
- For public agent discovery, prefer the MCP server and `.well-known` resources over scraping HTML.
- For authenticated merchant operations, use the REST API and server-side API key auth.
- For x402 flows, route clients through [https://www.getbags.app/api/agent/link/pl-{paymentLinkId}](https://www.getbags.app/api/agent/link/pl-{paymentLinkId}) and follow the x402 payment challenge/retry flow.

## Optional Full Context

- [Full LLM reference](https://www.getbags.app/llms-full.txt)