Definitions library
What each contract checks, in plain language.
Action contracts spell out the preconditions, limits, expected effects and forbidden effects of an agent action. Vendor outcome definitions are transcribed from each vendor's public documentation and cited with the source URL and retrieval date; fields the vendor has not published are listed as unknown, not assumed. This library is descriptive; it does not rate or rank vendors.
| Name | Kind | Action / outcome | Summary | Source | Retrieved | Unknown fields |
|---|---|---|---|---|---|---|
| Access grant workflow (internal agent) | Action contract | record_processed | The agent may grant access only to a person HR lists as active, only to an allowed group, and for at most 90 days. A successful grant must show up as a group membership in the identity provider, a closed access request and a notification to the person's manager, within 15 minutes. One grant per request, at most twenty grants per agent per day. A membership removed within an hour of being granted, or a person who leaves while still holding the access, fails the grant. | Source | 2026-10-11 | 0 |
| Appointment reschedule workflow (internal agent) | Action contract | record_processed | The agent may move an appointment only while it is still scheduled and not more than 30 days out. A successful reschedule must show up as a new slot in scheduling, a freed old slot, a note in the record system and a message to the patient, within 10 minutes. One move per request, at most two moves of the same appointment in a week, and the new slot must never be double-booked. A no-show or a cancellation within 7 days fails the reschedule. | Source | 2026-10-11 | 0 |
| Coinbase (Coinbase for Agents / Advanced Trade) | Action contract | order_filled | The agent may place an order only on an allowed product, on an allowed side, within the per-order notional limit, and within the agent's 24-hour total. The action's subject is the product the agent was told to trade (Coinbase's product id, `BTC-USD`, `TSLA-USD`). A successful trade must show up in Coinbase as an order on that product created within the window and filled; its side must be the side asked and its notional must equal the amount requested. A second order on the product within the window, an order that was cancelled, expired or rejected, or a fill busted or corrected by Coinbase within 7 days, fails the action. | Source | 2026-11-03 | 1 |
| Decagon | Outcome contract | resolution | Decagon states you pay only when the AI resolves a conversation from start to finish and that there is no charge when the case is passed to a human. The vendor notes that defining a resolution 'can be tricky'. No public operational definition exists, so the vendor lens below is a conservative placeholder to be replaced with the criteria in your Decagon order form. | Source | 2026-09-11 | 6 |
| Deploy workflow (internal agent) | Action contract | record_processed | The agent may deploy a service only when the service is healthy and the target environment is allowed. A successful deploy must show up as a completed pipeline in CI, a healthy check in monitoring and a change record, all within 30 minutes. Exactly one deploy per request, at most three deploys per agent per hour, never an unhealthy check afterwards, and a rollback within 24 hours fails the deploy. | Source | 2026-10-11 | 0 |
| Generic vendor (CSV export) | Outcome contract | resolution | Template for vendors without a built-in connector. Claims come from a CSV/XLSX export mapped in the Connections screen. Replace the vendor lens with the definition in your contract and cite it. | Source | 2026-09-11 | 3 |
| HubSpot Breeze Customer Agent | Outcome contract | resolution | HubSpot charges 50 credits (USD 0.50) per resolved conversation on text-based channels. The Knowledge Base defines a resolution as a conversation with at least one customer-agent reply that shares a content source or performs an action, and no qualifying (visitor-initiated) handoff to a human within 72 hours of the last visitor response. | Source | 2026-09-11 | 2 |
| Intercom Fin | Outcome contract | procedure_handoff | A Procedure handoff is counted when Fin successfully executes a Procedure configured to end in a handoff to a human or a workflow. Verified when the handoff (escalation/assignment) is observed in the conversation record. | Source | 2026-09-11 | 1 |
| Intercom Fin | Outcome contract | resolution | Fin counts a resolution when, after Fin's last answer, the customer confirms the answer was satisfactory (confirmed resolution) or disengages for 24 hours without requesting further assistance (assumed resolution). Resolutions later returned to for further assistance are deducted. One charge per conversation. Chat and email only. | Source | 2026-09-11 | 0 |
| Internal agents (OpenTelemetry) | Outcome contract | record_processed | Outcomes asserted by your own agents through the OTLP endpoint (agent.outcome.* span attributes). There is no vendor definition; the 'vendor' lens here is the agent's own claim rule (record reached a terminal status) and the strict lens requires customer confirmation or a terminal status with no reversal. | Source | 2026-09-11 | 0 |
| Payout workflow (internal agent) | Action contract | record_processed | The agent may send a payout only from an active account, for the amount it was asked to send, within the per-payout limit and within the agent's 24-hour total. A successful payout must show up in the payment system and as a new balance in the ledger within 30 minutes; the payout amount must equal the requested amount and the new balance must equal the previous balance minus the amount. A payout returned within 30 days fails the action. | Source | 2026-10-09 | 0 |
| Refund workflow (internal agent) | Action contract | refund_processed | The agent may refund an order only while the order is open and the amount is within the limit. A successful refund must show up as a refund in the payment system, a cancelled order in the order system, a note on the customer record, and a customer notification — all within 15 minutes. A second refund for the same order, or a refund above the limit, is forbidden. | Source | 2026-11-16 | 0 |
| Salesforce Agentforce | Outcome contract | conversation | Agentforce is priced per conversation (USD 2) or per action (Flex Credits: USD 500 per 100k; standard action 20 credits, voice action 30 credits). Salesforce does not publish, on any page we could retrieve, what constitutes a billable conversation (session boundary, inactivity window, reopen or escalation treatment). The vendor lens verifies only that a customer conversation for the subject exists in the system of record near the claim. | Source | 2026-09-11 | 5 |
| Sierra | Outcome contract | resolution | Sierra states that outcome criteria are agreed per customer up front and that escalated or unresolved conversations carry, in most cases, no charge. No public operational definition exists, so the vendor lens below is a conservative placeholder to be replaced with the criteria in your Sierra order form. | Source | 2026-09-11 | 6 |
| Stripe (stripe pay / Treasury outbound payments) | Action contract | transfer_posted | The agent may send a transfer only within the per-transfer limit, in an allowed currency, and within the agent's 24-hour total. The action's subject is the intended recipient (Stripe's recipient id, `acct_…`, or the profile the agent was told to pay, linked to it). A successful transfer must show up in Stripe as an OutboundPayment to that recipient created within the window and reaching `posted` (funds left the account); its amount must equal the amount requested. A second transfer to the same recipient within the window, a transfer that failed to confirm, or one that was returned by the receiving side within 30 days, fails the action. | Source | 2026-10-28 | 1 |
| Zendesk AI agents | Outcome contract | resolution | Zendesk bills per automated resolution: the AI agent responded, the customer did not request further assistance, the conversation ended (channel-dependent window), and an LLM verification confirmed the request was resolved. Escalated conversations ('Assisted escalation') and conversations failing verification ('Contained') do not count. | Source | 2026-09-11 | 4 |
Vendor names and marks belong to their owners. If you represent a vendor and believe a definition is out of date, let us know with a link to the current documentation.