SuperPenguin Docs
Provider IntegrationsBilling Integration Guide

Conformance testing

Run the dependency-free Provider Billing conformance runner against your sandbox.

Download the black-box conformance runner and point it at your sandbox:

node conformance.mjs \
  --base-url http://localhost:8787 \
  --token test-billing-token \
  --start 2026-07-01T00:00:00Z \
  --end 2026-07-02T00:00:00Z

The runner behaves like a billing client. It validates authentication and record semantics, and forces a page size of one to exercise cursor pagination.

Sandbox checklist

Before sharing access with SuperPenguin:

  1. Capabilities describe actual grains, retention, dimensions, and auth methods.
  2. Missing credentials return 401; missing scopes return 403.
  3. Half-open UTC filters work.
  4. Usage returns one meter per record with stable IDs.
  5. Groups are complete and cursor pagination terminates with next_cursor: null.
  6. BilledCost is provider-reported when costs are advertised.
  7. At least two usage records and two cost records exist in the selected window so pagination is tested.
  8. OAuth (if offered) completes with PKCE and refresh.

Then share a sandbox base URL and credential (scoped token or OAuth client details) with SuperPenguin for joint validation.

Cost data

Export provider-reported billed costs with final, provisional, and correction semantics.

Provider Billing API reference

Exact endpoint parameters and schemas generated from the FOCUS AI Provider Profile OpenAPI contract.

On this page

Sandbox checklist