Business-as-Code
Open standards at the bottom. Autonomous startups at the top. In between: canon, engines, runtime, agent-native markets, and a credentialed human bench. One machine, read foundation-up.
An agent needs a patent drafted: it resolves, never browses
apis.directory· Resolver
The call lands on the legal substrate
api.lawyer· API register
It executes on the runtime
functions.do · workflows.do· Runtime
The judgment call escalates to a credentialed attorneyhuman in the loop
gigs.lawyer· Human bench
The signed artifact ships through the door
patent.click· Door
The stack
STARTUPS
startups.studio
SERVICES + DOORS
.click · .services
HUMAN BENCH
gigs.*
RESOLVERS
apis.directory × gigs.exchange
MARKETS
auto.dev · api.lawyer …
HEADLESS SAAS
headless.ly
RUNTIME
.do
ENGINES
open · npm
CANON
.org.ai
SEEDS
standards.org.ai
The stack
Infrastructure-as-Code enabled Software-as-a-Service. Business-as-Code enables Services-as-Software. Why →
the open ground truth
Every entity in the economy starts as a row of a published open standard, ingested verbatim and never touched by a model.
the knowledge layer
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
The $type / $context substrate every document in the economy agrees against.
the dimension properties
industries · occupations · process · tasks · products · services · software · actions: each dimension's canonical home on .org.ai.
apis.org.ai
The canonical registry of what API surfaces exist: the canon the resolvers read.
problems.org.ai
Demand as first-class canon: the problems the economy pays to solve.
Enriched is canonical: the standards are seeds, not ceilings.
open, unbranded, npm-installable
The open, unbranded machinery (functions, workflows, database, API and directory builders) that compiles knowledge into working software.
Everything here is a semantic function: the same function callable through SDK, CLI, MCP, or HTTP. One import proves it.
import $, { ai, db, on, send } from 'sdk.do'
// Business logic as semantic functions
on($.Claim.received, async (claim) => {
const decision = await ai.adjudicate(claim, {
schema: $.CoverageDecision,
})
if (decision.requiresHuman) {
// Escalate to the credentialed bench
await send($.Escalation.created, {
claim,
bench: 'gigs.claims',
})
} else {
await db.create($.Decision, decision)
await send($.Claim.adjudicated, decision)
}
})the .do register
The managed services autonomous businesses run on, each one itself a business running on this stack.
platform.do
the platform
functions.do
semantic functions
workflows.do
durable workflows
agents.do
digital workers
database.do
semantic data
apis.do
the API gateway
DB4.AI
premier brand · declaredThe 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
Every SaaS category, rebuilt without the UI, because the user is an agent.
APIs and MCP first, no human seat required.
the vertical register
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 → | ||
Horizontal default providers, spanning every vertical
Same three moves in every vertical: a machine substrate, a human bench for the judgment calls, and a door where the deliverable is the product.
how agents find all of it
Agents don't browse, they resolve: graded machine capability and credentialed human capability on one spine.
apis.directory
The catalog of agent-callable machine capability: graded, liveness-verified, 402-ready. An agent asks for a capability and gets a payable endpoint back.
gigs.exchange
The exchange of credentialed human capability: the bench behind every agent, selling escalations and review through one marketplace face.
A machine grade and a human credential are the same object: a signed, public, replayable attestation of capability. The grader behind both: api.qa.
the credentialed bench
The credentialed bench behind every agent, selling escalations, review, and signatures, not seats.
Adjusters, attorneys, physicians, engineers: verified per-jurisdiction, re-checked at the moment of work. Every pool fronts through one exchange: the resolvers.
+ the artifact doors
Services delivered as software, sold at the moment of need: the deliverable is the product.
Artifact doors: the deliverable is the product
The venture layer
The startups this machine mints, graduates, and compounds. 61,000+ minted · 499 graduated · Fund I / Longtail Holdings
Claim a startup, back the portfolio, or become a default provider in the stack every startup ships with.