List your product as a capability

The model

A capability is any service reached through a single paid URL. You keep running your product exactly as it is today, and Tael sits in front of it as a metered gateway that handles payment on every request.

• A buyer calls your capability with one Tael API key.
• Tael verifies the USDC payment on Stellar, then proxies the call to your real endpoint and returns your response unchanged.
• You are paid per call, in USDC, automatically. You never see the buyer's wallet, and the buyer never sees your upstream key.

On the buyer's side, the entire integration is a single line of code:

import { Tael } from "@tael/sdk";
const tael = new Tael({ apiKey: process.env.TAEL_KEY });

// your product, called and paid for with one key:
const result = await tael.post("your-product", { ...input });

What you can list

A capability can take any of the following forms. Choose whatever fits your product.

• API. Any REST or HTTP endpoint, such as a weather service or an OCR engine.
• MCP. A Model Context Protocol server or a single tool from one.
• Agent. A hosted agent that accepts a task and returns a result.
• Model. An inference endpoint, for example a language or image model.
• Dataset. A paid data feed or query endpoint.

What you need

• A paid HTTP endpoint that Tael can call on each request, using GET or POST.
• Upstream authentication, if any. If your endpoint needs a key, you hand it to Tael once, and Tael injects it on the server for every call. Buyers never see it.
• A price per call in USDC, where fractions of a cent are perfectly fine.
• A Stellar payout address where your earnings land. It must hold a USDC trustline for Tael's issuer (see below), or payments are rejected on-chain.

Pricing & fees

You set the price per call. Whatever you choose becomes the amount a buyer pays in the 402 challenge for your capability.

Tael charges a marketplace fee of 1% on each call, taken in the very same USDC transaction. Because settlement is non-custodial, your share lands directly at your payout address. On a $0.010 call, for instance, you keep $0.0099 and Tael takes $0.0001. There are no monthly fees and no minimums.

Publish it

Sign in to the dashboard with your Stellar wallet, open My Capabilities, and add one. The wizard walks you through it in four short steps:

• Describe. Name your capability, choose its kind, and add its endpoint, your price per call, and your Stellar payout address. If your endpoint needs a key, set the auth scheme (Bearer, or a header such as x-api-key) and paste the key. It is encrypted and injected on the server, so buyers never see it.
• Test. Run each request live against your real endpoint. Tael captures the actual response and uses it as the public sample, so what buyers see is what your API truly returns.
• Answer. Reply to a short set of AI-generated questions about your capability. Your answers become its public FAQ.
• Publish. Your capability goes live in the marketplace immediately and is callable by any Tael key. It starts marked Pending review until Tael verifies it (see below).

The Quickstart walks through the whole flow end to end.

Verification

Every capability carries a status that tells buyers how much Tael has vetted it. Publishing never blocks on this, and it never limits what your capability can do. It is purely a signal of trust.

• Pending review. The state every new third-party capability starts in. It is fully live: listed in the marketplace, discoverable, and callable, and you earn on every call from the moment you publish. It simply has not yet been reviewed by the Tael team, so it shows a neutral Pending badge rather than the green check.
• Verified. A trust badge that only the Tael team grants, after we review the capability. Verified capabilities carry the green check that buyers look for, and they rank ahead of unverified ones in discovery.

To move from Pending to Verified, make sure your listing is accurate and complete: a clear description that matches what the endpoint returns, a working live test, an answered FAQ, and a payout wallet that holds the required USDC trustline (see What you need). Then reach out to the team through your capability contact or our community channels, and we will review it. There is nothing extra to build.

First-party and partner capabilities. Some capabilities are verified by Tael from day one. These include our own first-party model capabilities, where Tael wraps providers such as Claude and Grok so any agent can call a frontier model with a single key and pay for it by the token in USDC, and our vetted ecosystem partners such as Nebula for on-Stellar agentic actions and TrustLine for agent credit lines. These arrive Verified because we run or directly vet them, which is the same bar we hold every other capability to before granting the badge.

Onboarding prompt

The quickest way to map your product onto Tael is to paste the prompt below into your own LLM, whether that is Claude, ChatGPT, or anything else. It interviews you, uncovers every part of your product worth exposing, and produces a capability manifest you can hand straight back to us, so we can list you with the widest surface and the least back and forth.

You are helping me put my product on Tael, the payment layer for AI agents.
I want to list my product as one or more capabilities on Tael, so that anyone can use it
with a single Tael API key and pay me per call in USDC on Stellar. Your job is to map my
product onto Tael's capability model and produce a concrete capability manifest that I can
hand to the Tael team.

## How Tael works
- A capability is any service reached through a paid URL of the form https://<tael-gateway>/c/<slug>.
- A buyer calls that URL with a Tael API key. Tael verifies the USDC payment on Stellar, then
  proxies the call to my real endpoint and returns my response. I get paid per call automatically,
  and I never touch the buyer's wallet.
- The requirement is simple: I expose a normal HTTP endpoint (GET or POST) that Tael calls on each
  request. Tael injects my upstream credentials on the server, so buyers never see my key.
- A capability can be any of these kinds: api, mcp, agent, model, or dataset.
- I set a price per call in USDC. Tael takes a marketplace fee of about 1% in the same transaction,
  and I keep the rest, settled to a Stellar address I choose.

## What I want from you
1. If I have not told you already, ask me what my product does and how it is accessed (its endpoints,
   tools, and authentication).
2. Find the largest surface I can reasonably offer. List every endpoint, tool, dataset, or model I
   could expose as a capability, because each one is another way for people to pay me.
3. For each capability, produce one row of a manifest with these fields:
   - name, kind (api, mcp, agent, model, or dataset), and a one-line description
   - the endpoint URL and its HTTP method
   - how Tael should authenticate to my upstream (Bearer, x-api-key, a custom header, or none)
   - the request shape (its parameters or body) and a sample response
   - a suggested price per call in USDC, with a short reason
4. Flag anything that does not fit a plain paid HTTP endpoint, such as streaming, stateful sessions,
   MCP over HTTP, or on-chain signing, and suggest how to adapt it.
5. Ask me for my Stellar payout address, and remind me it must hold a USDC trustline for Tael's
   issuer (shown on the publish form) or payments will be rejected on-chain.

## Output
Return the completed manifest as a table, followed by a short note on anything that needs a custom
adapter. Optimize for the most value: list everything worth exposing, not just a single endpoint.

Send the finished manifest to the team and we will get your capabilities live. The more you expose, the more ways people have to pay you.