Skip to content
LogoLogo

Publish pricing.md

The price list agents read

View as Markdown

pricing.md is a Markdown file that lists your paid endpoints, what each costs, the tokens it accepts and where to send requests. Agents read it to find out what you sell before they call.

Radius builds the file from your policy, so it changes when your prices do.

What the file lists

Your organization has one pricing.md. It opens with your organization's name and a short note on how to pay, then has a section per published catalog. A catalog is one project's paid endpoints.

## Reports API
 
- Base URL: https://api.example.com
- Payment: x402, SBC on Radius
 
### Report lookup
 
- Request: `GET /reports/:id`
- Price: $0.002 / request
- Free: 20 requests per 5 minutes per IP
 
### Bulk export
 
- Request: `POST /reports/export`
- Price: $0.05 / request
- Rate limit: 10 requests per second per caller

This is the file as Radius writes it: prices are in US dollars per request, with a $. An endpoint with rules for verified agents also carries a Who pays line, and a catalog in test mode carries Mode: test (no real money), so agents know nobody pays real money.

Publish a catalog

  1. Set the project's Base URL in its Settings. Without it, agents see prices but not where to call.
  2. Open the project's Catalog page.
  3. Select Publish.

The status badge shows Published, Not published, or Nothing to list when no endpoint charges yet. Unpublish takes the catalog out of the file.

To publish several projects at once, open the pricing.md menu on the organization overview and select Manage.

Publishing needs the endpoints:write permission.

Where it is served

FileAddressServed by
Organization's filehttps://app.radiustech.xyz/<organization>/pricing.mdRadius, without sign-in
A project's own filehttps://<your base URL>/pricing.mdYour Worker, through the SDK

Both update within a few minutes of a price change or a publish.

Serve it on your own domain

Agents look for pricing.md on the domain they are about to call. With pricingMd: true, a Worker running @radiustech/platform-sdk serves the project's catalog at /pricing.md with only that project in it.

// src/index.ts
import { withRadius } from '@radiustech/platform-sdk';
export { RadiusCounter } from '@radiustech/platform-sdk/limiters/do';
 
const handler = {
  async fetch(request, env, ctx) {
    return handle(request, env);
  },
} satisfies ExportedHandler<Env>;
 
export default withRadius(handler, { pricingMd: true });
  • The file appears once the catalog is published and has a paid endpoint. Until then, /pricing.md goes through the policy to your handler.
  • Requests for /pricing.md are answered before the policy, so they are never charged or counted.
  • The Base URL line is RADIUS_PUBLIC_URL when set, otherwise the request's origin.
  • The file is stored in the RADIUS_POLICY KV namespace and synced on the same schedule as the policy.

A Hono app needs both halves: pricingMd: true on the middleware, which serves the file, and syncPricingMd() in its scheduled() handler, which fetches it.

// src/index.ts
import { radiusPolicy, syncPolicy, syncPricingMd } from '@radiustech/platform-sdk';
import { Hono } from 'hono';
 
export { RadiusCounter } from '@radiustech/platform-sdk/limiters/do';
 
const app = new Hono<{ Bindings: Env }>();
app.use('*', radiusPolicy({ pricingMd: true }));
 
export default {
  fetch: app.fetch,
  scheduled: (_controller, env, ctx) => {
    ctx.waitUntil(syncPolicy(env));
    ctx.waitUntil(syncPricingMd(env));
  },
} satisfies ExportedHandler<Env>;

Add your own details

The published file lists catalogs and prices only. To add contact details, terms or anything else, copy it from the pricing.md menu, extend it, and host it on your own domain.

Next steps