Developer reference

Read the catalog as JSON.

Find a capability, follow its guide, or read its endpoints without loading the catalog interface. These public GET routes need no account or API key.

Public routes

/catalog/manifest.json
All capabilities, with stable IDs, category, providers, price metadata, example prompts and canonical reading URLs.
/catalog/capabilities/search-x.json
One capability and its endpoints. Replace search-x with any capability ID in the manifest.

Start with the manifest and follow detail_url for the capability you need.

const catalog = await fetch('https://taskfuel.ai/catalog/manifest.json').then(r => r.json());
const capability = catalog.capabilities.find(c => c.id === 'search-x');
const detail = await fetch(capability.detail_url).then(r => r.json());

Schema 1.0

Both responses include schema_version, documentation_urland source. The source names the provider specifications and their export date. The manifest also includes counts and a capabilities array.

Capability fields
FieldMeaning
idStable capability identifier, such as search-x.
name, descriptionThe job and what it returns.
categoryCategory ID and name.
urlThe existing tool guide where one covers the capability, otherwise its catalog fragment.
guide_urlTool guide URL, or null where there is no dedicated guide.
detail_urlThe public JSON response for this capability.
providersProvider names and domains serving callable endpoints.
example_promptAn example task for an agent.
endpoint_countCallable endpoints, excluding supporting calls.
priceStructured USD pricing, defined below.

A detail response has one capability object and an endpointsarray. Each endpoint names its provider, HTTP method, URL, description and price.supporting_call identifies uploads, status polls and other helper operations.

Price fields

currency is USD. Capability amount is the smallest positive declared endpoint amount, with type: "from" andbasis: "lowest_positive_declared_endpoint_amount". When no such amount is available, amount is null andtype is quote_required.

Endpoint price types are fixed, from, range,free, quote_required and unlisted. Ranges use minimum and maximum; other types useamount. Their basis is provider_specification.quote_required is true where a price needs a request quote or is unlisted. On a capability, it also signals that at least one endpoint has no declared amount.

unit is null because the catalog export does not retain metering units. The number alone does not establish a per-call, per-token, per-second or per-result rate. Use TaskFuel discovery to read a provider's input schema and obtain a request quote with dry_run: true before spending.

Use a capability

Browse the catalog, read therequest and quoting instructions, or choose a tool guide.

/catalog/data.json remains the compact payload for the catalog interface. /capabilities.jsonremains available in its existing format.