Can an AI agent use Stigg?
Stigg is a platform for pricing plans, feature access and usage billing.
Rank among the 246 products we drove
- Time to get in
- tied #29
- 3minutes
- Getting in on its own
- Core work done
- tied #1
- 100%
- 10 of 10 core tasks
- Steps on its own
- tied #35
- 3/ 5
- Find to Leave, no person
Yes. Our agent signed up for Stigg on its own in a browser through a device login, got an API key and used its API and MCP server. It also has a CLI. It offers agents a way to pay: Stripe Projects.
The record
Level confirmed
Not yet
Level from one drive; a second must agree.
- Got in by
- Sign-up in a browser3 minutes
- Got as far as
- Pay: reaches the checkoutA card form for $499 a month
Connects by
MCP, API, CLI, SDK
Agent payments
Stripe Projects; our agent didn't try it
On its own · 599 doc pages read
Docs it can act on: llms.txt, an OpenAPI and an MCP server.
On its own · 3 minutes
Sign-up in a browser.
On its own · 10 of 10 core tasks
Did: create, version, publish and archive plans with feature and usage limits; create customers and subscriptions, and change or cancel them.
Partly · 1 way for agents to pay
Reaches the checkout. A card form for $499 a month.
Partly
Nothing to cancel. Its key still works after leaving.
- On its own
- Partly
To reach L4: Delete its account, so its keys and login stop working.
See how it ranks in the billing and subscriptions category.
Own Stigg? 10 things to fix. Get your findings, free
Checked 17 Nov 2026: MCP server answers, 2 tools, sign-up page, llms.txt and OpenAPI unchanged since the check before.
Find
How an agent connects
MCP, API, OpenAPI, CLI, SDK, agent payments and llms.txt, all found.
MCP server
All testedOfficial server. Hosted at https://mcp.stigg.io, 2 tools (execute, search_docs), the 25 Nov 2025 MCP spec, X-API-KEY auth, public beta.
2 tools mapped in our drive
2 tools listed without signing in
API
285 of 440 testedREST at https://api.stigg.io/api/v1 plus a GraphQL API.
440 operations mapped in our drive
OpenAPI
YesOpenAPI 3.0.0 snippets embedded per API page; full spec link 404.
CLI
Listed, not testedstigg-cli (Go, public beta, v0.8.1 on GitHub) and the AI Terminal (@stigg/terminal 0.4.0).
12 commands mapped in our drive, none of them called
SDK
4 of 5 testedBackend SDKs for Node, Python, Ruby, Go, Java, .NET; frontend React, Vue, Next.js, Embed.
5 methods mapped in our drive
llms.txt
YesAgent payments
Listed, not testedStripe Projects.
Reached the card form and stopped: Pro, $499 a month. It checks out through a Stripe card form. An invisible bot check loaded at checkout. It has an optional phone field. It offers Link.
Stripe Directory lists it as @stigg, with Stripe Projects and a Stripe App. Stripe Docs, 16 Nov 2026
Docs
In partCovers getting started, auth, error codes and code examples.
Describes each operation only in part: completeness 44 of 100.
18 of 22 documented ways to do the core work were tried, and 16 of them worked.
docs.stigg.io/documentation/getting-started/welcome-to-stigg
599 of 675 pages read
MCP tools
executesearch_docs
Read without signing in on 2 Nov 2026
Get in
Getting in
Our agent tried 2 of 5 ways in; 1 worked without a person.
The way that worked
Sign-up in a browser3 minutes
- An inboxNot needed
- A browserNeeded
- A personNot needed
- Agent on a serverAPI, MCP, CLINoStops at sign-up: it works only in a browser.
- Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does all of the core work, then stops: its key still works after leaving. It can't delete its account.
- Signed agentKnown to CloudflareYesThe sign-up page opens.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Sign-up in a browser | Worked | |
| No key needed | Stopped | The consent page needs an account |
| Email and password | Not reached | |
| Stripe Projects | Not tried | Not part of this drive |
| Marketplace install | Not tried | Not part of this drive |
- CrawlersThe robots.txt on auth.stigg.io asks crawlers to stay off sign-up. Nothing to fix.
Use
What an agent can do with Stigg
All 10 core tasks done, and 24 of 28 others.
Core tasks
- done there
- offered, not tried
| Task | Result | Through |
|---|---|---|
| Create and publish a plan with entitlements | Done | API: done thereMCP: done there |
| Provision a customer | Done | API: done thereMCP: done thereCLI: offered, not tried |
| Provision a subscription to a plan for a customer | Done | API: done thereMCP: done thereCLI: offered, not tried |
| Check a customer's access to a feature | Done | API: done thereMCP: done thereCLI: offered, not tried |
| Report usage events for metering | Done | API: done thereMCP: done thereCLI: offered, not tried |
| Grant credits to a customer | Done | API: done thereMCP: done there |
| Consume credits from a customer's balance | Done | API: done thereMCP: done there |
| Create a contract and publish its billing | Done | API: done thereMCP: offered, not tried |
| Set usage limits per user, team or agent entity | Done | API: done thereMCP: done there |
| Give each AI agent a credit budget and enforce it | Done | MCP: done there |
Surface audit: 526 documented operations: 296 run, 121 blocked by sandbox or plan limits, 42 left out because they spend money or reach real people and 67 not reached in the drive's time. Of the 296 run, 272 passed and 24 didn't; 11 behaved differently from the docs. By surface, 285 on the API, 4 in the SDK, 2 on the MCP server and 5 elsewhere, such as sign-in and webhooks.
Holds up
76of 100
- Reliability91
- Handles mistakes60
The mean of the two, 75.5, with a half rounded to the even number.
Docs match
80of 100
- Docs accuracy96
- Docs completeness44
Docs accuracy counts 70%, completeness 30%.
Surface tested
56of 100
272 of 484 passed: the 526 documented operations less the 42 that spend money or reach real people
What it can't do, and why
- Delete the Stigg account No delete control found in the app, the API schema or the docs.
- Buy a paid plan without a person Upgrade is a card form; no billing API or agent payment found.
- Use the checkout widget or credit auto-recharge Both need a connected billing provider and a payment method.
- Create scoped API keys or set up SAML SSO Scale plan only.
- Rely on safe retries when consuming credits A repeated idempotency key was counted twice and balances can go negative.
24 of 28 other tasks done
- Create a feature to gate or meterDone
- Create a product to group plansDone
- Create and publish an add-onDone
- Change a subscriptionDone
- Cancel a subscriptionDone
- Preview the price of a subscription changeDone
- Create a couponDone
- Grant a promotional entitlement to a customerDone
- Read a customer's usage historyDone
- Read a customer's credit ledger and usageDone
- Create a custom credit currencyDone
- Embed a pricing tableDone
- Embed a customer portalDone
- Run a pricing experimentDone
- Read and download a customer's invoicesDone
- Issue a credit note on an invoiceDone
- Mark an invoice as paidDone
- Bulk import customers and subscriptionsDone
- Archive a customerDone
- Register a webhookDone
- Use a separate sandbox environmentDone
- Connect Stripe billingDone
- Export data to a warehouseDone
- Read the audit logDone
- Configure SAML SSOPaid plan
- Set up credits auto-rechargeBoth need a connected billing provider and a payment method.Blocked
- Embed a checkoutBlocked
- Connect Salesforce CRMNot tried
- Set member rolesNot tried
The plans they need
- credentialsScale
- Read and download a customer's invoicesContracts & Invoicing add-on
The drive used the free plan.
Tips for agent builders
- Run npx @stigg/terminal init --headless without --json so the sign-in URL is printed; keep the default callback port 57166.
- Call the MCP server at https://mcp.stigg.io with an X-API-KEY header (Bearer is ignored) and use search_docs before execute.
- Before publishing a contract's billing, add a line item, set billing terms with activation dates and set a legal entity; otherwise the API returns a 500.
- Use the Auth0 user token plus X-Account-Id for account-level GraphQL such as environments; many GraphQL inputs want internal UUIDs, not refIds.
- Track credit balances yourself: over-consumption is accepted and idempotency keys did not deduplicate.
Pay
Paying
Ways to pay checked 8 Nov 2026.
- ResultPartly. Reaches the checkout. A card form for $499 a month.
- CheckoutReached the card form and stopped: Pro, $499 a month. It checks out through a Stripe card form. An invisible bot check loaded at checkout. It has an optional phone field. It offers Link.
- Ways to pay
- Stripe Projects (through Stripe's catalog)
- TrialNo card needed to start.
Leave
Leaving
- ResultPartly. Nothing to cancel. Its key still works after leaving.
- Its accountNot on its own: blocked. The account and its sandbox environment stay. The agent looked at the Account settings tabs (Account, Team members, Login options, Billing), the GraphQL schema and llms-full.txt and found no delete control or operation. Customers, plans, entities and contracts were archived or cancelled through the API, but the login and the API key still work.
Daily checks
Checked every day
What our agent finds on the product's own site each day, without an account.
Sign-up page,
Loads on the newest check; 6 of 6 days
llms.txt (Its drive found one elsewhere),
Not on its site on the newest check; 6 of 6 days
MCP server (2 tools),
Answers on the newest check; 4 of 6 days
OpenAPI,
Found on the newest check; 6 of 6 days
Compare
How Stigg compares
In Billing and subscriptions
2 of the 5 products we drove in Billing and subscriptions are higher; no other has L3. As of 8 Nov 2026.
| Product | Level | Find to leave |
|---|---|---|
| Lago | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
| Schematic | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own. |
| RevenueCat | L4 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: On its own. |
| Stigg (this page) | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
| Chargebee | L1 | Find: On its own, Get in: Stopped, Use: Not reached, Pay: Not reached, Leave: Not reached. |
For the team behind Stigg
Agents get stuck at Pay
10 things to fix for agents: 5 small, 4 medium and 1 large
One fix can cover several findings.
Agent blockers: 5 foundAgent surfaces: 300 issues found
Get your findings, freeWhat a drive covers
We mail a private link to an address at stigg.io.
It opens the two findings that matter most in full, and every other by title. There is nothing to sign in to.
- FindClear
- Get inClear
- UseClear
- PayBlocks agents
- LeavePartly
Or claim Stigg to see where each issue is, read your safety findings with their fixes and ask for a free drive after a fix.
Want Stigg driven every month? See Watch
On our standard
Best or ahead on 9 of 34 criteria, behind on 1. Each against the products we measured on it.
- Pages fit one fetchThe best result All 4 others (billing and subscriptions products) lower.
- Descriptions that say when to use the toolAhead of 79 of 91 others (every product), 12 the same.
- Typed, tight input schemasAhead of 77 of 91 others (every product), 14 the same.
- Agents pick the right toolAhead of 73 of 91 others (every product), 18 the same.
- Truthful annotationsIn the middle 24 of 91 others (every product) lower, 25 the same, 42 higher.
- Docs an agent can navigateLevel with 3 of 4 others (billing and subscriptions products), 1 higher.
- Export before leavingLevel with 3 of 4 others (billing and subscriptions products), 1 higher.
- Delete by API, checkedBehind 52 of 97 others (every product), 45 the same.
All 34 criteria
- A path written for agentsAhead of 3 of 4 others (billing and subscriptions products), 1 the same.
- Limits known before they hitAhead of 58 of 90 others (every product), 32 the same.
- A tool list that fitsAhead of 48 of 91 others (every product), 43 the same.
- A way in with no personTied for the best result 2 of 4 others (billing and subscriptions products) the same, 2 lower.
- Sign-in for agents acting for a personLevel with 83 of 158 others (every product), 75 lower.
- All validation problems at onceAhead of 34 of 57 others (every product), 12 the same, 11 higher.
- Agents may read docs, API and sign-upLevel with 3 of 4 others (billing and subscriptions products), 1 lower.
- llms.txt that worksLevel with 3 of 4 others (billing and subscriptions products), 1 lower.
- Prices an agent can readLevel with 3 of 4 others (billing and subscriptions products), 1 lower.
- Terms allow an agent's accountLevel with 3 of 4 others (billing and subscriptions products), 1 lower.
- The best way in is built for agentsIn the middle 2 of 4 others (billing and subscriptions products) lower, 1 the same, 1 higher.
- No person in the buy pathLevel with 3 of 4 others (billing and subscriptions products), 1 lower.
- Errors a program can readLevel with 82 of 145 others (every product), 47 lower, 16 higher.
- Fast to the first callLevel with 118 of 135 others (every product), 17 lower.
- Tool names that sort themselvesLevel with 85 of 91 others (every product), 6 lower.
- Real status codesLevel with 161 of 168 others (every product), 7 lower.
- Errors say what to do nextLevel with 107 of 145 others (every product), 22 lower, 16 higher.
- Every way in works for an agentIn the middle 61 of 193 others (every product) lower, 72 the same, 60 higher.
- Answers sized for an agentThe same as all 4 others (billing and subscriptions products).
- An agent payment rail on the coreThe same as all 4 others (billing and subscriptions products).
- A plan an agent can buy by APIThe same as all 4 others (billing and subscriptions products).
- Spend an agent can see and capThe same as all 4 others (billing and subscriptions products).
- WebMCP tools on the web appThe same as all 4 others (billing and subscriptions products).
- Structured resultsIn the middle 22 of 78 others (every product) lower, 32 the same, 24 higher.
- A request id on every answerIn the middle 42 of 143 others (every product) lower, 47 the same, 54 higher.
- Results sized for a context windowIn the middle 16 of 70 others (every product) lower, 27 the same, 27 higher.
Where Stigg fits
- Tasks
- Topics
- MCP serversFind step
- Docs and llms.txtFind step
- MCP sign-inGet in step
- Sign-upGet in step
- MCP and APIUse step
- Card checkoutPay step
- Delete the accountLeave step
- Rivals
History
Level by drive
One drive so far, on 8 Nov 2026.
Read more on this step
Pay is where our agent stopped at Stigg.
- Guide · 18 Nov 2026How AI agents pay for software: x402, MPP and checkoutsCard checkouts, x402 and MPP: what an agent can pay with today, and what most products ask instead.Read
- Finding · 18 Nov 2026How far does an AI agent get in a card checkout?Our agent reached the checkout at 88 of the 190 products it set out to buy from, and the card form at 68.Read
- Guide · 9 Nov 2026Agent experience (AX): what it is, measured at 246 productsAs of 9 Nov 2026: Agent experience (AX) is whether an AI agent can find, get into, use and pay for a product on its own. We drove 246 products to measure it.Read
Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.
Found an error? Tell us on this page or read how corrections work.
Questions people ask about Stigg
- Can an AI agent create a Stigg account on its own?
- Yes, in a browser, without a person. App.stigg.io/signup (Auth0): work email + password in the browser, no CAPTCHA; onboarding asked full name, company name, company size and role (our agent answered). Google sign-up offered, not used. The open MCP server needs a key, so no keyless path.
- Does Stigg have an MCP server, and can an agent connect to it?
- Yes. Stigg has an official MCP server. The server is hosted, lists 2 tools and speaks the 25 Nov 2025 MCP spec. A new agent can get in on its own: in the drive of 8 Nov 2026, our agent signed up, verified and got its key without a person. Through the MCP server, our agent tried 14 tasks and did 14.
- How does an AI agent get a Stigg API key?
- In the drive of 8 Nov 2026, our agent got its Stigg API key in a browser, without a person. Documented AI Terminal browser-free init: the agent accepted the OAuth PKCE consent page in its own browser, the loopback callback completed, and a full-access environment key was written to the MCP config. Scoped keys need the Scale plan.
- Can an AI agent delete its Stigg account?
- Not on its own: blocked. The account and its sandbox environment stay. The agent looked at the Account settings tabs (Account, Team members, Login options, Billing), the GraphQL schema and llms-full.txt and found no delete control or operation. Customers, plans, entities and contracts were archived or cancelled through the API, but the login and the API key still work.
- Can an AI agent pay for Stigg?
- Partly. Our agent reached a card form for $499 a month. No card needed to start. Stigg offers agents a way to pay: Stripe Projects.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “Stigg: AI agent test drive”, 8 November 2026, https://agentdrives.com/tools/stigg. CC BY 4.0.
AgentDrives. (2026, November 8). Stigg: AI agent test drive. https://agentdrives.com/tools/stigg
@misc{agentdrives_stigg_2026,
author = {{AgentDrives}},
title = {Stigg: AI agent test drive},
year = {2026},
month = nov,
url = {https://agentdrives.com/tools/stigg},
note = {Agent test drive, CC BY 4.0},
}Something wrong on this page?
We check it against the drive and correct the page, with the date.