Paying for YouSpot as an agent
What YouSpot sells, who can buy it, and the commerce protocols an agent can negotiate against: a UCP discovery profile at /.well-known/ucp and the ACP checkout surface.
The short version: an agent cannot buy YouSpot yet. A person can, and an agent can then work inside that account over OAuth. This page says so in the shape the commerce protocols define, so an agent learns it by reading rather than by guessing at a 404.
What is for sale
| Plan | Price | Included |
|---|---|---|
| YouSpot Free | $0 a month, no credit card | Use up to 50 credits/month |
| YouSpot Pro | $10 a month | Use up to 1,000 credits/month |
Every new account starts on YouSpot Free: sign up at https://youspot.com/pricing and it is provisioned with no card. YouSpot Pro is bought by a signed-in person from the same page, which hands over to Stripe. Credit packs are bought the same way from the billing tab. There is no seat count and no annual commitment.
What costs nothing: the docs MCP server at /mcp/docs, the sandbox MCP server at /mcp/sandbox, every markdown twin, /ask, and the read side of the A2A agent. None of them take a credential, so an agent evaluating YouSpot never has to pay to find out what it does.
What a credit is spent on
Only the model does. One credit per chat message and one per app run, charged after the work succeeded, so a failed turn costs nothing. Storage, syncing and file exchange are not metered at all: reading your graph, importing from a connected mailbox, syncing a HubSpot portal and downloading a file are free at any volume your plan allows.
| Action | Cost |
|---|---|
| Chat message, or an agent draft | 1 credit |
| App run (ImageGen, ProspectFinder, DomainValue and the rest) | 1 credit |
| Reading, searching or writing your graph over MCP or REST | free |
| Mailbox, calendar, HubSpot, LinkedIn and X sync | free |
| File upload and download | free |
What bounds the free half is not price but shape: a per-address rate limit, declared on every response in the RFC 9331 RateLimit headers, and a hard cap on object count and file size per plan. An agent that paces against the headers never meets either. See /docs/versioning for the header table.
UCP discovery
The business profile is published at https://youspot.com/.well-known/ucp against Universal Commerce Protocol 2026-08-25. It advertises the three transports an agent can reach YouSpot over (REST, MCP and A2A), the identity-linking capability that OAuth 2.1 provides, and an empty payment-handler registry.
The empty registry is the point rather than an omission. UCP requires the member to be present even when it holds nothing, which is how a reader tells "no agent payment handler" apart from "this profile forgot to mention one".
curl -s https://youspot.com/.well-known/ucp | jq '.ucp.payment_handlers, .checkout.status'
# {}
# "not_supported"ACP checkout
The Agentic Commerce Protocol endpoints exist and negotiate: POST /checkout_sessions and POST /agentic_commerce/delegate_payment. Both answer 501 with a protocol-level ACP error naming the version they speak, 2026-04-17. A preflight OPTIONS returns 204 and allows POST.
| Request | Answer |
|---|---|
OPTIONS /checkout_sessions | 204, Access-Control-Allow-Methods: POST, OPTIONS |
POST /checkout_sessions | 501 with type: service_unavailable, code: checkout_not_supported |
POST /agentic_commerce/delegate_payment | the same 501 |
The error carries only the four members the ACP schema allows, because it refuses additional properties: type, code, message and supported_versions. Everything an agent should do instead is in the message.
What would change this
Agent-initiated checkout needs a payment credential YouSpot can charge without a person present: a delegated payment token from the buyer's agent, or a stablecoin rail such as x402. Both are decisions about the product, not about this page. When one ships, the payment-handler registry in the UCP profile stops being empty and these endpoints stop answering 501.