Business-as-Code
The full stack of the autonomous service economy.
We turn open industry standards into software that does the work, then build the companies that sell it.
Water damage from a burst pipe
- Covered
- $8,400
- Deductible
- $1,000
- Paid to the policyholder
- $7,400
Delivered to a property manager in 6 min
Claims agent paid $7,400 and wrote back
Licensed adjuster signed off the payout
Claims agent checked the policy: covered, $1,000 deductible
Claims agent read the email and four photos
A property manager sent the request
Infrastructure-as-Code enabled Software-as-a-Service. Business-as-Code enables Services-as-Software.
-
The open ground truth
Seeds
Every entity in the economy starts as a row of a published open standard, ingested verbatim and never touched by a model.
- standards.org.ai
- NAICS
- O*NET
- UNSPSC
- APQC
- GS1 / EPCIS
- OpenAPI
- Zapier catalogs
-
The knowledge layer
Canon
The canonical, machine-readable knowledge layer of the economy, enriched beyond the standards it cites, open to every agent that can dereference a URL.
- schema.org.ai
- apis.org.ai
- problems.org.ai
- the dimension properties
Enriched is canonical: the standards are seeds, not ceilings.
-
Open and unbranded
Engines
The open, unbranded machinery (functions, workflows, database, API and directory builders) that compiles knowledge into working software.
- ai-functions
- ai-workflows
- ai-database
- api-builder
- dir
- graph-site
- autonomous-startups
- GitHub
-
The .do register
Runtime
The managed services autonomous businesses run on, each one itself a business running on this stack.
DB4.AI, the database built for agents. The stack runs on itself: every managed .do service is an autonomous startup on its own stack.
-
Software without the UI
Headless SaaS
Every SaaS category, rebuilt without the UI, because the user is an agent.
- headless.ly
- CRM
- billing
- support
- inventory
- HR
- + 25 more categories
APIs and MCP first, no human seat required.
-
+ the artifact doors
Services-as-Software
Services delivered as software, sold at the moment of need: the deliverable is the product.
- agentic.services
- patent.click
- trademark.click
- capcall.click
- boardpacks.click
- + the .co work-noun estate
One function, four protocols
Everything here is a semantic function: the same function callable through SDK, CLI, MCP, or HTTP. One import proves it.
import $, { send } from 'sdk.do' await send($.Claim.received, claim)
do send Claim.received ./claim-4821.json
await client.useTool('do', { script: 'await send($.Claim.received, claim)',})
curl https://apis.do/send/Claim.received \ -H "Authorization: Bearer $DO_API_KEY" \ --json @claim-4821.json
One API per vertical
One canonical API per vertical, engineered to be the answer a model gives when an agent asks.
| Vertical | API substrate | Human bench | Demand door |
|---|---|---|---|
| Automotive | auto.dev | Partner | Vin |
| Legal | api.lawyer | gigs.lawyer | patent.click |
| Sales | api.forsale | closers.sale | closers.deals |
| Insurance | api.insure | gigs.claims | the .claims estate |
| Supply chain | epcis.dev | customs.broker | visibility.cloud |
| Health / RCM | Partner to build this vertical | ||
| Construction | Partner to build this vertical | ||
| Real estate | Partner to build this vertical | ||
Resolved, not browsed
Agents don't browse, they resolve: graded machine capability and credentialed human capability on one spine.
The credentialed bench behind every agent, selling escalations, review, and signatures, not seats.
Graded, live, payable APIs. An agent asks for a capability and gets an endpoint back.
Credentialed people, verified per jurisdiction. An agent escalates and gets a signed decision.
The grader behind both. Every grade and credential is a signed attestation anyone can replay.
Startups, minted by the stack
Every layer below exists to make them. Claim one, back the fund, or see what has shipped.
The window is open
Open standards compiled into running businesses, with humans in the loop.