Commercial Control Plane

Commercial routes are deliberately separate from the intelligence API. External developers authenticate with a tenant member API key (beta) sent as Authorization: Bearer — see Authentication. Service JWTs and service principals are internal/enterprise mechanisms. GET /v1/billing/plans, GET /v1/catalog, and GET /v1/products/{slug} are public; POST /v1/billing/webhooks/polar verifies its Polar signature instead of bearer authentication.

Beta

Base URL: https://api.agentic.forwardlane.com
Auth: tenant member API key as Authorization: Bearer $FL_API_KEY.
Credits run in shadow mode during the beta: every call is metered and visible at GET /v1/billing/usage, but no charges are made.
Discovery: GET /v1/catalog (public) lists all 16 products with live/coming-soon status, summaries, and docs links; GET /v1/products/{slug} returns a live product’s descriptor (endpoints included) or a 501 coming-soon envelope with waitlist_url and docs_url.

Product discovery

Method	Path	Authorization	Contract
`GET`	`/v1/catalog`	Public	All storefront products with `slug`, `name`, `status`, `summary`, `docs_url`.
`GET`	`/v1/products/{slug}`	Public	Live: descriptor with endpoint list. Coming soon: `501` envelope. Unknown slug: `404`.

Billing and usage

Method	Path	Authorization	Contract
`GET`	`/v1/billing/plans`	Public	Active plan catalog.
`GET`	`/v1/billing/usage`	Member	Usage meters for the current organization.
`GET`	`/v1/billing/entitlements`	Member	Entitlement map for the current organization.
`POST`	`/v1/usage/events`	Owner/Analyst with `START_RUN`	Validated, idempotent usage event.
`POST`	`/v1/billing/checkout-session`	Owner	Creates a Polar checkout session.
`POST`	`/v1/billing/portal-session`	Owner	Creates a Polar customer-portal session.
`POST`	`/v1/billing/webhooks/polar`	Polar signature	Processes verified billing updates.

{
  "plan_id": "plan_team",
  "success_url": "https://app.example.com/billing/success",
  "cancel_url": "https://app.example.com/billing"
}

{
  "session_id": "checkout_123",
  "url": "https://checkout.polar.sh/...",
  "plan_id": "plan_team"
}

CLI bridge and reports

Method	Path	Purpose
`POST`	`/v1/cli/pair`	Issue or exchange a CLI pairing code.
`GET`	`/v1/cli/config`	Read organization, workspace, role, meters, and entitlements for a paired CLI.
`POST`	`/v1/cli/runs`	Register a tenant-scoped CLI run.
`GET`	`/v1/cli/runs`	List organization-scoped CLI runs.
`POST`	`/v1/cli/publish`	Publish a run and its usage record.
`POST`	`/v1/tenant/service-principals/{credential_id}/revoke`	Revoke a tenant credential.
`POST`	`/v1/reports`	Create an organization-scoped report.
`GET`	`/v1/reports/{report_id}`	Retrieve an organization-scoped report.

Report creation and usage events accept idempotency keys so callers may safely retry network failures. All tenant reads and writes are organization scoped; never reuse one organization’s credential in another workspace. See API Schemas for the request and response field contracts.

Get Started

Products

API Reference

CLI

FL Web

Python SDK

MCP Server

Graph Schema

Commercial Control Plane

Commercial Control Plane

Beta

Product discovery

Billing and usage

CLI bridge and reports

​Commercial Control Plane

​Beta

​Product discovery

​Billing and usage

​CLI bridge and reports

Commercial Control Plane

Beta

Product discovery

Billing and usage

CLI bridge and reports