A1 ratingsTogether AITogether Code Interpreter

Together Code Interpreter

Together AI · tool · Any industry Provisional
B
BGrade
67Score
±1595% range
≈#120Rank of 1134
0%From fleets
FR-CAT-01570Catalog no.
Provisional: the range is wide because some facts are thin or not yet known. It narrows as research and fleets fill in.

The six pillars

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

Can you see what it costs?

Vendor cost API (GET /v1/billing/usage returns cost-annotated usage line items by month/day (beta; access must be requested from support)) · 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?

Cost analytics dashboard groups spend by product, line item, project or API key (project/key grouping in beta)
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?

partial
50±59
Not known yet. Sits at a neutral 50 with a wide range until facts arrive · 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?

Spend cap: Hard cap · Per-agent keys: Scoped · Revoke: Console only · SSO: SSO only
79±27
Desk research 91 · 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 research52%Neutral starting point48%

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 capHard cap
Per-agent keysScoped
Audit logNot known
RevokeConsole only
SSOSSO only
PricesPublished

Spend cap is the org-level prepaid balance: API access stops at $0 (budgets and spend alerts are 'coming soon'; no per-key spend or rate limits). API keys are scoped to projects (multi-project in early access). SSO via SAML/OIDC on Scale and Enterprise only, set up by Together staff; SCIM is on the roadmap, not shipped. No audit log documented.

History

11-12 B 6711-13 B 6711-14 B 6711-15 B 6711-16 B 6711-17 B 6711-18 B 67
Rated since 2026-11-12. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-11-11.

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-11-11 [1][2][3][4] Correct
Prices published
Cost
Yes Declared
medium confidence
2026-11-11 [1][2][3][4] Correct
Usage API
Usage
Cost analytics dashboard groups spend by product, line item, project or API key (project/key grouping in beta) Declared
high confidence
2026-11-11 [1][2][3][4] Correct
Cost per agent
Per agent
partial Declared
high confidence
2026-11-11 [1][2][3][4] Correct
Per-agent keys
Controls
Scoped Declared
medium confidence
2026-11-11 [1][2][3][4] Correct
Revoke access
Controls
Console only Declared
medium confidence
2026-11-11 [1][2][3][4] Correct
Spend cap
Controls
Hard cap Declared
medium confidence
2026-11-11 [1][2][3][4] Correct
SSO
Controls
SSO only Declared
medium confidence
2026-11-11 [1][2][3][4] Correct
Small plans get the data
Small plans
No Declared
high confidence
2026-11-11 [1][2][3][4] Correct

Prices · $0.03 per 60-minute session.

Notes · One bill per organization. Prepaid credits unless on a sales contract. api_key_id attribution covers inference and code interpreter requests only, so per-agent attribution works only if each agent gets its own project API key.

Scored with the rubric for Agents and agent platforms (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 Together Code Interpreter?

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.