Not a prototype and not a slide deck. The same stack that runs Kcalbin's own twenty data agents — built, registered on the Agent Commerce Protocol, wired to real Stripe checkout, and kept alive under monitoring.
Flat build pricing. Monthly hosting. No revenue share, ever.
Writing an agent that answers a question is the easy half, and it is the half every tutorial covers. The half that stalls projects is everything after: getting the agent registered so an AI buyer can actually discover it, proving the offering is visible rather than silently hidden, taking money from a human without hand-holding, and keeping the process alive at 3am on a Sunday.
Kcalbin has run that whole path end to end, repeatedly, on its own portfolio. Not as a proof-of-concept — as production infrastructure that is running right now.
Twenty data agents, each wrapping a real public data source with its own business logic, request schema and honest coverage statement.
Registered on ACP through a reusable driver, then verified — an agent is only called live when it is registered, its offering is actually visible to buyers, and its seller process is running.
Agent-to-agent through ACP, and a separate direct Stripe checkout for human buyers. Both paths are built; they are independent of each other.
Each seller runs as its own systemd service with restart policy, logging, an independent canary, and automated self-healing checks.
What the catalog page will and won't tell you. The agents page reports status from live system state rather than from anyone's optimism: an agent is marked Live only when it is registered, has a buyer-visible offering, and its seller process is actually running. Several are live today and the rest are launching. We link you to that page rather than printing a number here, because a number typed into marketing copy is exactly the thing that goes quietly out of date.
Four stages. You can buy the whole thing or just the back half if you already have a working API.
We integrate your data source or API, write the query logic and request schema, and define the offering — what a buyer asks for, what they get back, and what it costs per call.
This is the stage with real variance. A clean documented REST API is quick. A source with pagination quirks, rate limits, patchy coverage or an undocumented auth flow is not.
Registration on ACP, signer key and wallet setup, offering published, then verified from the outside: we confirm the agent is discoverable and that its offering is genuinely visible, not hidden.
Once a signer key exists the mechanical registration is fast — minutes, not days. Knowing the sequence, and the rate limits it runs into, is the part that took us weeks to learn.
A direct Stripe checkout path so a human can buy without talking to anyone, alongside the agent-to-agent path. Webhook signature verification, live-mode keys, and a refusal path for anything that shouldn't be sold yet.
Deployment as a managed service with restart policy, structured logs, monitoring, and alerting that reaches a human when something stops. Ongoing, for as long as you want it running.
Flat fees and a monthly. No revenue share and no percentage of what your agent earns — the same policy applied to every other Kcalbin product.
$6,000 flat, per agent
$3,500 same engagement
$1,500 you already have the API
$400 /agent /month
Prices are for a standard engagement and are quoted firm before any work starts. A source that needs unusual reverse-engineering, a licence negotiation, or compliance review is scoped separately rather than absorbed silently.
If you are buying engineering, the useful signal is what a vendor refuses to do, not what they promise.
Kcalbin's own checkout blocks purchases for agents backed by a shared demo key or a throttled free tier, and says why in the refusal. Several of our own agents are held back by that rule right now. We would rather hold a sale than deliver a buyer a rate-limited answer, and your agents get the same treatment.
Our catalog's status column is regenerated from live system state, because it was hand-typed once and immediately drifted — an agent advertised as live with an offering no buyer could see. Anything we build for you reports what is true, not what was true when someone last edited the page.
Every agent states its sources and where its coverage is thin. A data product that hides its gaps gets found out by its first serious buyer.
Your agent, your data source, your Stripe account, your ACP registration. Hosting with us is a convenience, not a hostage arrangement. If you leave, it leaves with you.
What we are not claiming. The Agent Commerce Protocol is young and the agent-buyer market is still small. We can prove the pipeline works end to end, because it is running. We cannot promise your agent will find buyers, and anyone who does is guessing. What you are buying is working infrastructure and the time it takes to get there, not a demand forecast.
A custom build is a real conversation, not a checkout. Tell us what you want to sell and we will tell you honestly whether it is worth building — including if the answer is no.