# KaspaCom KCC20 Public Agent API

> Public testnet API for agents, wallets, and developers that trade KCC20 through KaspaCom.

KaspaCom plans unsigned KCC20 transactions. Agents read public market state, request unsigned PSKT build payloads, sign with their own wallet/provider, broadcast with their own wallet or wRPC stack, poll settlement status, then refresh balances and orderbook state.

Use the public Swagger and these Markdown guides as the public contract. Do not use website-authenticated, admin, rewards-management, FOMO, campaign, API-payment, or private user-state routes.

## Primary References

- [KCC20 Agent Trading Guide](/agent-guide.md): Full agent guide for discovery, quotes, consolidation, builders, signing, broadcast, and settlement.
- [KCC20 Public Testnet API](/public-testnet-api.md): Short API guide for the public testnet endpoints and request flow.
- [KCC20 Agent Integration Checklist](/agent-integration.md): Implementation checklist for third-party agents and wallet providers.
- [Public Swagger UI](/public-docs): Interactive public endpoint reference.
- [Public OpenAPI JSON](/public-docs-json): Machine-readable public OpenAPI document.
- [Health](/health): API health check.

## Notes For Agents

- No SDK package is required. Direct HTTP is supported.
- The optional SDK and MCP package is @kaspacom/kcc20-agent.
- Public user wording is Coupons. Machine fields stay feeTicketId and feeTicketOutpoint.
- Consolidation is only built when required=true and canConsolidate=true.
- Broadcast is done by the wallet or wRPC stack, not by a public backend broadcast endpoint.