A1 ratingsSpyneSpyne

Spyne

Spyne · feature · Dealerships & auto sales
D
DGrade
31Score
±1095% range
#1024Rank of 1134
0%From fleets
FR-CAT-00807Catalog no.

The six pillars

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

Can you see what it costs?

Only emailed invoices · prices on request only
23±27
Desk research 12 · 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?

No usage API found
14±27
Desk research 0 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

Nothing a buyer can read
14±27
Desk research 0 · 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?

HTTP step in a workflow · Developer API (docs.spyne.ai) for sending vehicle media; no usage or billing endpoint documented.
57±27
Desk research 60 · 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
59±13
Desk research 60 · 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
14±27
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 research74%Neutral starting point26%

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
RevokeNot known
SSONot known
PricesOn request

Single enterprise API key plus category key copied by an Admin from Dev Tools; no scoping or revocation documented.

History

11-12 D 3111-13 D 3111-14 D 3111-15 D 3111-16 D 3111-17 D 3111-18 D 3111-19 D 31
First rated 2026-10-02 at 30 (D). Now 31. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.

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
Only emailed invoices Declared
medium confidence
2026-10-13
1 earlier
[1][2] Correct
Prices published
Cost
No Declared
medium confidence
2026-10-13 [1][2] Correct
Usage API
Usage
None found Declared
medium confidence
2026-10-13
1 earlier
[1][2] Correct
Cost per agent
Per agent
None found Declared
medium confidence
2026-10-13
1 earlier
[1][2] Correct
How an agent reports out
Reports out
HTTP step in a workflow Declared
medium confidence
2026-10-13
1 earlier
[1][2] Correct
Per-agent keys
Controls
Not scoped Verified 2026-10-26
1 earlier
[1][2] Correct
Small plans get the data
Small plans
No Declared
medium confidence
2026-10-13
1 earlier
[1][2] Correct

Prices · No public prices (Lite and Pro plans, Talk to Sales); custom contract priced by monthly inventory volume, rooftops and features

Notes · Contract-priced automotive merchandising AI; Developer API access included in Lite and Pro. Enterprise API key copied by an Admin from the dashboard Dev Tools tab; no usage, credit or billing endpoint documented.

Scored with the rubric for Features inside a larger product (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

Run agents on Spyne?

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.