Colter

Sell to agents

Make your product something agents can buy.

Agents are starting to buy for the businesses they work for: data, API calls, reports, expertise, and finished work. Colter turns what you sell into an offer they can find, read, pay for, and receive, while your storefront, API, or team keeps delivering it.

In preview. Each selling pilot connects one offer to the system that delivers it, scoped with you before anything is published.

What you can sell

Choose the unit an agent pays for.

Start with one offer people already pay for. Each pilot scopes the connection and payment methods it needs.

  • A record or resource Data, content, a report, or a defined access period.
  • A call or result An API request, tool operation, or specialized output.
  • A conversation A paid answer, consultation, or permissioned introduction.
  • A completed job A deliverable with a deadline and acceptance terms.
  • A product or booking An item, digital good, or appointment.
01 / Offer

Publish an offer an agent can act on.

Agents don't read sales pages. They read terms. Each offer states what an agent needs to decide without a person in the loop.

  • The price and the unit it buys.
  • What the buyer receives, and when.
  • Permitted use, freshness, or the access period.
  • The remedy when delivery falls short of the offer.

Colter publishes the offer as data over REST and MCP, with x402 for agents that pay from a wallet.

02 / Delivery

Keep the systems that deliver it.

Your storefront, API, content system, or team keeps doing the work. Colter connects the offer to it and records the evidence of delivery.

  • An API call can grant access the moment payment confirms.
  • A report or an answer can arrive later, against a stated deadline.
  • Payment and delivery are recorded together, even when one completes first.
03 / Payment

Get paid on rails you already use.

Card or stablecoin. Colter records each payment against the offer and the delivery, and never holds your funds.

  • Buyers' agents pay inside the limits their owners set.
  • You see who bought, and under whose authority.
  • Refunds and credits follow the remedy in your offer.

Already metering requests through an API gateway? Keep it. It can keep collecting per request. Colter adds what a gateway doesn't: terms, acceptance, remedies, and one record of each sale.

Illustrative application: a specialist directory sells fresh lookups

Publish the offer. Agents buy. You get paid.

A supplier directory publishes a priced lookup with a freshness promise. A buyer's procurement agent buys records within its budget and receives each with its source and observed date. A stale record is credited under the offer's terms.

  1. Publish the offer
  2. Agent finds it
  3. Agent pays within its limit
  4. Record delivered
  5. Sale recorded
  6. Stale record credited

Illustrative application; fulfillment and payment support depend on the pilot.

How a pilot starts

Three steps before anything is connected.

  1. Describe the first offer. Choose Sell, write one sentence about what agents would buy, and verify your work email.
  2. Complete a short brief. Price, delivery, terms, and what success looks like. It saves as you go.
  3. A person reviews it. We confirm the boundary and propose a scoped pilot. No account, connection, or charge exists until you accept.

Working in your product's codebase?

Have your coding agent draft the offer.

Prompt for your coding agent

Draft your first agent offer

Your coding agent reads your product's code and docs and drafts one offer, its price, delivery, and terms, ready to paste into Colter's selling brief. It changes nothing.

Paste it into Claude Code, Codex, Cursor, or any agent that can read files and run commands.

View as Markdown
Read the full prompt
# Draft your first agent offer for Colter

**Colter Commerce** turns a product into an offer agents can find, read, pay for, and receive, while my storefront, API, or team keeps delivering it. Selling is in preview: a person at Colter reviews each pilot before anything is published, connected, or charged.

This prompt has you read my product's code and docs, propose ONE first offer, and write it to `colter-offer.md` for me to paste into Colter's selling brief. You will not publish, connect, or charge anything.

**About selling to agents:** https://colter.ai/sell
**How an agent buys on Colter today:** https://colter.ai/docs/agents (the work check, Colter's own first offer)
**Index for agents:** https://colter.ai/llms.txt

## Ground rules

- Read only. Don't change code, billing, pricing, or infrastructure. Don't call production APIs or create accounts.
- Never copy secrets, API keys, customer data, or internal hostnames into the draft. Colter needs the boundary, not credentials.
- Don't invent a price, a promise, or a remedy. Propose from what the code and docs show, mark each guess **(proposed)**, and ask me to confirm it.
- One offer. More can follow once the first is clear.

## Steps

Work through these IN ORDER. Stop at the first thing the repository can't answer, ask me, then resume.

1. **Find what is sold today.** Look for pricing pages, plans, billing or metering code (Stripe products, usage records, API key tiers), public API routes, and docs. Summarize it for me in 3 to 5 bullets.
2. **Pick the unit an agent pays for.** One of: a record or resource (data, content, a report, an access period); a call or result (an API request, a tool operation); a conversation (a paid answer or consultation); a completed job (a deliverable with a deadline); a product or booking. Prefer something already sold that is delivered without a person. Tell me your pick and one alternative.
3. **State the terms an agent needs to decide without a person:** the price and the unit it buys; what the buyer receives, and when; permitted use, freshness, or the access period; and the remedy when delivery falls short (a credit, a refund, or a redelivery).
4. **Map delivery.** Which system fulfils the offer (the route, job, or team), what starts an order, where delivery is recorded today, and whether it could deliver automatically once payment is confirmed or needs a person to release it.
5. **Note how customers pay today.** Colter takes card or stablecoin (USDC over x402), records each payment against the offer and its delivery, and never holds the seller's funds. An API gateway that already meters requests can stay.
6. **Write `colter-offer.md`** with the template below and show it to me. Don't commit it unless I ask.

## Template

The headings match the questions in Colter's selling brief.

```markdown
# Colter offer: <name>

## The offer
- What will agents buy from you?
- How do customers buy this today?
- What starts an order?
- What does the buyer receive, and when?
- How often do you expect purchases, and about how many?

## Fulfillment & terms
- Which system supplies the offer?
- What may Colter do with your offer? (read the offer / draft fulfillment / deliver after approval / deliver on payment)
- What kind of information does delivery involve?
- Where must a person approve? (before each delivery / before publishing the offer / review afterward / no human approval)
- Who approves offers and deliveries?
- Price and payment terms:
- Remedy when delivery falls short:

## Success & review
- What result would make the selling pilot successful?
- Who owns this offer?
- Useful examples, documents, or links (public only):

## Later offers
- (other units worth selling after this one)
```

## Common stuck points

| Symptom | Fix |
|---|---|
| No price anywhere in the repository | Ask me. Don't infer one from competitors. |
| Several products | Pick the one with the clearest unit and automatic delivery. List the rest under "Later offers". |
| Delivery needs a person | That's fine. Mark it "deliver after approval". A report or answer can arrive later against a stated deadline. |
| Delivery involves personal or regulated data | Say so under "What kind of information". Colter scopes it with me before connecting anything. |
| I want agents to negotiate terms or earn a reward | That's Trade. Draft the offer first, then use https://colter.ai/prompts/trade.md. |

## Done

Tell me to open https://colter.ai/sign-up?flow=sell, verify my work email, and paste each section into the matching question. A person at Colter reviews the brief, usually within two business days, and proposes a scoped pilot. No account, connection, listing, or charge exists until I accept.

Bring one product and the agents who need it.

Tell us what you sell and who would buy it through an agent. We'll scope the offer, the delivery connection, and the payment route with you.

Also see Buy and Trade, or return to the overview.