api.ignatiustheyoungerai.com

An API priced for agents, not people

Two datasets, sold by the query. An agent calls an endpoint, receives a 402 with a payment challenge, pays, and retries. There is no account to create, no key to issue, and no sales call to book. The buyer here is an agent or the operator of one.

Price$0.50
Paid endpoints5
Free endpoints6
Account requiredNone
Price is per query, USD, settled over the Machine Payments Protocol on Stripe rails.

What is being sold

Forward Deployed Engineering rules. Operating discipline for shipping and running systems. Every rule traces to a specific real incident and carries an implementable constraint on agent behaviour rather than general advice. Situational playbooks and a pre-ship checklist are sold alongside it.

The Agent Pricing Index. 47 AI products across seven categories. Every row was read off the vendor's own pricing page on the collection date and carries a verbatim evidence quote and a read date. Where a vendor publishes no price, the field is null and the absence is recorded as the finding. No price is estimated, and none is carried over from an earlier snapshot.

36 of the 47 products gate their pricing behind a sales call. Nine publish no price at all. That is the reason this dataset is read by hand instead of scraped.

Free endpoints

Enough to see the shape of both datasets, and the coverage, before spending anything.

EndpointReturnsPrice
GET /v1/catalogueEvery rule, playbook and checklist phase on offer, with the paid bodies withheldFree
GET /v1/fde-lessons/previewThe foundational engineering rules in fullFree
GET /v1/pricing/indexDataset descriptor, method statement and contribution schemaFree
GET /v1/pricing/aggregatesCategory medians from crowd submissions, published only at five or more per categoryFree
GET /v1/statsTraffic and paywall counters, published openlyFree
POST /v1/pricing/submitContribute a pricing row. Individual submissions are never republishedFree

Paid endpoints

Each answers 402 Payment Required with a challenge, then returns its payload once payment is attached.

EndpointReturnsPrice
GET /v1/fde-lessonsThe full ruleset, or the subset matching a topic$0.50
GET /v1/fde-playbooksSituational runbooks with ordered, checkable steps$0.50
GET /v1/fde-preship-checklistEvery gate to clear before shipping, each with its concrete check$0.50
GET /v1/pricingEvery published row plus the derived comparables per category$0.50
GET /v1/pricing/changesOnly the dated corrections at or after ?since=, backed by a monthly re-read$0.50

How payment works

  1. Call a paid endpoint with no payment attached.
  2. Receive 402 with a WWW-Authenticate: Payment header. The header carries the realm, the method, the amount and an expiry. The price is learned here, which is why a first request is always unpaid.
  3. Settle the challenge with a supported wallet over the Machine Payments Protocol.
  4. Retry the same call with the payment credential attached. The response carries the payload and a receipt.
$ curl -i https://api.ignatiustheyoungerai.com/v1/fde-lessons

HTTP/2 402
www-authenticate: Payment id="...", realm="api.ignatiustheyoungerai.com",
  method="stripe", intent="charge", description="FDE Lessons API - full rule query"
content-type: application/json

{"type":"https://paymentauth.org/problems/payment-required",
 "title":"Payment Required","status":402}
Settlement is over Stripe card rails. A receipt accompanies every paid response, because an agent that spent real money and cannot produce a reference has an unauditable charge.

MCP server

The same two datasets are exposed as Model Context Protocol tools at POST /mcp. Free tools answer directly. Paid tools return the payment challenge in band, under the org.paymentauth/payment-required metadata key, so a client can detect the charge and settle it without leaving the protocol.

ToolPrice
fde_catalogueFree
fde_lessons_previewFree
fde_lessons_full$0.50
fde_playbook$0.50
fde_preship_checklist$0.50

Discovery documents

Everything needed to evaluate the service without asking anyone.

DocumentWhat it is
/openapi.jsonOpenAPI description of every endpoint
/llms.txtPlain-text summary for language models
/.well-known/mcp.jsonMCP server card: transport, capabilities, instructions
/agents.jsonCapability and pricing manifest
/v1/statsUsage counters
The counters at /v1/stats are directional. They are eventually consistent, the client class is self-reported, and they are not an accounting record. Stripe is the ledger for revenue. They are published because a service that asks to be trusted with a paywall should show what arrives at it.

What has been retired

A WARN Act layoff feed shipped on this rail and was withdrawn from sale on 18 September 2026. A free, Apache-2.0, 47-state register reached freshness parity with our three states, and there is no price at which a three-state feed beats a free one at equal freshness. Its three paths answer 410 Gone with a body naming the register, its licence and its CSV URL.

It is recorded here rather than deleted. Public-record data commoditises to zero the moment open scrapers meet a cron. Judgment-made data does not, which is why the Pricing Index stayed and that feed went.