Pricing
Bounded evaluations, agreed in writing.
No public prices yet. Every offer states its scope, its limits, its data terms and who pays for compute.
- ConversationOne conversationPrice No offer yet
- Assisted comparisonBetween
- Shadow analysisBetween
- Evaluation4–6 weeksPrice Agreed in writing
- Continuation1 yearPrice Agreed in writing
Compare the programs
Conversation
One recent cross-team change, reconstructed with you before anything is shown.
One conversationPrice No offer yet- A recent change, reconstructed
- Decisions and owners mapped
- Agent-operation time counted
- Agents run by AssentNot in this program
Whether there’s a feasible security path
Evaluation
Four to six weeks on one nominated cross-team relationship, measured against your best setup.
4–6 weeksPrice Agreed in writing- One nominated relationship
- Decision and owner setup
- Agent runs within agreed limits
- An evaluation scorecard
A cancellation boundary
Continuation
For a bounded engineering group, offered only where the evaluation measured value.
1 yearPrice Agreed in writing- A bounded engineering group
- Reusable decision context
- Delegated agent execution
- Evidence
No promise of unlimited inference or agent runs
A proposed program, untested with buyers. The paid evaluation needs a build that runs live, which doesn’t exist yet. Until then, we start with a conversation about one of your recent changes.
Prices are agreed in writing for each offer. Any figure we test stays an experiment until buyers accept it, so none is published here.
Compare the programs
The evaluation stage is planned as a paid, bounded engagement, and every offer states who pays for agent compute.
| ConversationOne conversation | Evaluation4–6 weeks | Continuation1 year | |
|---|---|---|---|
| Scope | One recent change | One relationship | A bounded group |
| Written scope and baseline | Not in this program | Included | Included |
| Data terms before access | Included | Included | |
| Execution model stated | Included | Included | |
| Included analysis and execution limits | Included | Included | |
| Success measures | Included | Included |
Who pays for agent compute?
Every offer states it up front: either your organization’s own provider accounts, or usage managed by Assent with a visible meter and caps.
Your organization’s provider accounts
The provider would bill agent compute to you, and you would see the full spend. The platform fee would cover Assent, including the runner infrastructure.
- Provider terms must permit the use
- Personal subscriptions would never be pooled
Assent-managed execution
Assent would pay for compute and recover it through a stated allowance and meter. None of the metering is built yet.
- Caps and a visible meter
- A known pause, or an expansion you approve, at the cap
- No surprise usage fees
What would a first evaluation involve?
One nominated cross-team API relationship in one GitHub repository, with a versioned OpenAPI definition, identified provider and consumer owners, and a runnable contract or integration test.
Over four to six weeks we’d aim for five to ten eligible real changes, compared with your normal workflow and your best improved one, including your agent vendor’s own orchestration where you have it. People approve decisions and merge throughout.
Design partners
Bring one recent cross-team change.
We reconstruct it with you before showing a solution: the decisions, their owners and the effort, agent operation included.