What we take on
- Micro-SaaS APIs. A single-purpose service, priced per call rather than per seat or per month, scoped so one endpoint carries the whole product.
- M2M payments. Pay-per-request billing over x402 on the Base network: a signed authorization for an exact amount, settled per call, with no card, account, subscription, or standing spending allowance.
- A2A and agent discovery. The surfaces an agent needs before it can transact — an A2A agent card and JSON-RPC endpoint, an OpenAPI contract, a capability descriptor,
llms.txt, and an MCP server — generated from the same live configuration as the payment challenge, so none of them can drift from what you actually charge. - Operations. Rate limiting, sanctions screening, allowlisted logging, and the legal and compliance pages a payment underwriter reads.
What we build on
We build machine-executable API primitives for autonomous agents, LLM pipelines, and automated M2M systems. They run edge-native on Cloudflare Workers and Durable Objects: no origin server to keep alive, no cold start to absorb, and a published JSON Schema for every response, so a caller can parse the answer without a model in the loop. Our own Hydrate/Dehydrate and Verify endpoints are built exactly this way, and what they return is what their schema says they return.
How an engagement works
Scope
You describe the outcome and the deadline. We come back with what we would build, what we would leave out, and what it costs.
Build
Work ships in reviewable increments against the agreed scope, not as a single delivery at the end.
Launch and list
The service goes live with its payment challenge and its discovery surfaces at the same time, so agents can find and pay it from the first day.
Run it, or hand it over
We can operate what we build — hosting, monitoring, and changes — or hand over the repository and the runbook.
Commercial terms
Client work is quoted per engagement and invoiced in US dollars by SLIDINGBOX LLC. Fixed scope is quoted as a fixed fee; open-ended work is billed against an agreed rate and cap. Per-call API pricing for our own products is published on the pricing page and is separate from project work.
What we do not do
- Staff augmentation or open-ended retainers with no defined outcome.
- Work involving protected health information, payment-card data, or other regulated-data categories.
- Cryptocurrency exchange, custody, investment, or money-transmission services.
What we have built for ourselves
Hydrate/Dehydrate and Verify are our own micro-SaaS services, live in production and paid per call over x402. They are the working reference for everything above: see what we run and the security model behind it.
Tell us what you need
There is no sales process and no qualification call to book. Describe what you want built and we will tell you whether we are a good fit for it.