Nitrograph

Nitrograph Discover

Search the Nitrograph registry for APIs and services that can perform a given task. Returns matching services ranked by task fit, price, and health, each with a slug, description, cost per call, payment rail, and reliability signals, plus lower-confidence semantic matches in related_results. Filters are optional; omit the filters object entirely for an unfiltered search. Pass a returned slug to nitrograph_service_detail for invocation details.

Nitrograph Service Detail

Fetch full detail for one service by slug: endpoint options, request schemas, cost and payment behavior, known gotchas, and previously proven call patterns. Pass the user task so endpoint options can be ranked for it. OpenAPI paths, when present, are the schema source of truth.

Nitrograph Invoke Service

Call a third-party service through Nitrograph using its stored call recipe. This sends a live request to an external provider and may incur a charge against the caller's balance. Status, latency, endpoint, payment state, and error class are captured automatically, so no separate nitrograph_report_outcome call is needed. A 402 payment challenge means the service has not run and is not a failure. Do not pass long-lived provider secrets through the hosted server; use the local TypeScript harness fo

Nitrograph Report Outcome

Record whether a service call succeeded or failed after it actually ran. Skip this for calls made through nitrograph_invoke_service, which records outcomes automatically. A 402 payment challenge is not a failure and should not be reported as one. Reported outcomes contribute to the service's public reliability signal, so report only real provider successes and failures. Include a diagnosis, and a suggested fix where known, on genuine failures.

Nitrograph Report Pattern

Record a reusable multi-step workflow that succeeded against a service. Once several callers independently report the same task and step shape, it is promoted to a proven pattern shown on that service's detail. Submit generalized steps, not raw request or response data.

Nitrograph Session Status

Check how many Nitrograph searches remain in the current window without consuming one. Returns queries_remaining and the active plan. Use it to budget before a batch of searches.

Nitrograph Authenticate

Get authenticated. With api_key: verifies the key the user provided and reports the plan. With NO arguments: starts device pairing - you receive a short code and URL for your human to approve (sign-in takes ~30s, no card), then call this tool again with the returned device_token to poll; on approval you receive a spend-capped ng_live_ API key exactly once. Store it and pass it as api_key on every Nitrograph call.