A1 ratingsPikaPika API

Pika API

Pika · platform · Any industry
B
BGrade
69Score
±1395% range
≈#88Rank of 1134
0%From fleets
FR-CAT-01504Catalog no.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Vendor cost API (GET https://api.dev.pika.art/billing/balance; GET /billing/spend/daily (by API key and model, filter by api_key_id); GET /billing/monthly/YYYY-MM (+/csv)) · prices published
86±27
Desk research 100 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.

Can you see how much it's used?

Per-job billing.charge_micro_usd on settled jobs
90±17
Desk research 100 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

Exact, per key or project
90±17
Desk research 100 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.

Can an agent on it report out?

50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.

Can you control spend and access?

Per-agent keys: Not scoped · Revoke: Console only
60±27
Desk research 64 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).

Does it work on small plans?

Small plans don't get the data
10±17
Desk research 0 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.

Where the evidence comes from

Independent fleets0%Desk research64%Neutral starting point36%

Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.

Controls on record

Spend capNot known
Per-agent keysNot scoped
Audit logNot known
RevokeConsole only
SSONot known
PricesPublished

Dashboard lets you create, rotate and revoke keys; no key scopes documented. No per-key or per-org budget cap documented (postpaid orgs have an invoice cycle limit, prepaid balance acts as a gate). SSO and audit log not mentioned.

History

11-12 B 6911-13 B 6911-14 B 6911-15 B 6911-16 B 6911-17 B 6911-18 B 6911-19 B 69
Rated since 2026-11-01. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-31.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
Vendor cost API Declared
high confidence
2026-10-31 [1][2] Correct
Prices published
Cost
Yes Declared
medium confidence
2026-10-31 [1][2] Correct
Usage API
Usage
Per-job billing.charge_micro_usd on settled jobs Declared
high confidence
2026-10-31 [1][2] Correct
Cost per agent
Per agent
Exact, per key or project Declared
high confidence
2026-10-31 [1][2] Correct
Per-agent keys
Controls
Not scoped Declared
medium confidence
2026-10-31 [1][2] Correct
Revoke access
Controls
Console only Declared
medium confidence
2026-10-31 [1][2] Correct
Small plans get the data
Small plans
No Declared
high confidence
2026-10-31 [1][2] Correct

Prices · API Club membership $10/mo returned as $10 API credit; per-generation member rates (e.g. MiniMax H3 T2V 2K $0.13/sec) including a 5% platform fee; enterprise volume discounts up to 70% with commitment.

Notes · Prepaid org balance by default; postpaid invoicing available with an invoice-cycle limit. Spend is reported per API key, so one key per agent gives exact attribution.

Scored with the rubric for Platforms and APIs (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Corrections

1 awaiting review. Accepted corrections are published in the corrections register with an FR-C number.

Run agents on Pika API?

Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.