A ceiling on AI spend, and a front door agents can find.
No platform team required. A limit that holds, and one listing an assistant can act on.
Four situations.
- AI tools cover more ground, and nothing caps their spend.
- An agent going wrong is an unexpected bill, or a mistake a customer finds first.
- No IT function. Whoever is least busy owns it.
- Customers ask assistants for quotes, with no governed way through.
A ceiling, a lane, and a listing.
The same three at five people or five hundred.
A limit enforced before execution
Reserved before the work starts, captured only on success. Checked ahead of the action it is a limit. After the invoice it is a report.
Guardrails that name what stopped you
Rules read in order. Anything outside the lane stops and names the rule.
Terms an agent reads before buying
Publish your offer with its contract: the payload, the fields you never take, the price. Any assistant reads it without an account.
Each product, mapped to the job it does here.
Only the use cases that genuinely apply in this industry are listed.
Your business, listed where assistants shop
Publish what you sell and what a qualified customer request must include. Leads arrive verified, consented, and receipted, and listing is free.
Marketplace listing · verified lead delivery · settlement + signed receipts
Readable with no account
Any assistant can read your listing's terms over the same MCP endpoint they already speak. Want the listing content sharpened for agent readers? The Merchant toolkit and Concierge tiers do that as content work, never placement.
Open MCP discovery · agent-readable terms · listing optimization tiers
A ceiling your AI cannot talk past
Spend limits hold before execution, guardrails name what stopped you, and every action lands on a record you can read later.
Gateway checkpoint · policy + review queue · governed data sharing · receipts
One listing, from a local installer.
Sodzilla, sod installation, South Pinellas County
A licensed installer publishing one listing: a qualified sod-installation lead. It names the payload a buying agent sends, the fields it never takes, and the consent required.
Every request is identified, checked, and recorded. The difference between being found by an agent and scraped by one.
Read the listing → · The full story →Shipped, and what is still a conversation.
This matters more at your size, because nobody absorbs surprises.
Available today
- Spend caps enforced per request
- Ordered guardrails, first match wins
- A hard stop at the ceiling, with a reason
- A plain record of what each agent did and cost
- A free tier, 1,000 transactions a month
- A listing any agent discovers, no account needed
Not claimed today
- Getting live is a short working session. Self-serve signup is roadmap work.
- Splits are recorded and an operator resolves payouts. Automation is roadmap work.
- Billing is arranged directly and invoiced monthly.
The two we hear first.
How much setup is this really?
Am I too small for this?
One listing and one ceiling is a real start.
Capping what your tools spend, publishing what you sell, or both.
Request access