Investor Inquiries
AI workers need authority. Not constant supervision.
EMILIA is the authority control plane for autonomous work. A human or institution defines a finite operating mandate once; agents work unattended inside it; Gate enforces each consequential unit of work where money, code, permissions, records, or infrastructure can change.
Gate accepts native mandates and credentials from A2A, AP2, OAuth, and hardware-backed approval systems, then enforces them once at the executor. The A2A/AP2 integration is experimental; independent interoperability is not yet claimed.
The problem
Identity proves who or what is present. Policy describes what is generally allowed. Neither defines the finite job an autonomous worker may perform under current limits.
The product
The customer defines mission, limits, evidence, expiry, delegation, and exception rules once. Gate verifies the exact unit of work, reserves bounded authority, and controls provider entry through a customer- or partner-controlled executor adapter. Local risk signals may tighten, review, suspend, or refuse—never expand the mandate.
The adoption loop
The open local Authority Brain maps supported declared action surfaces and names blind spots. The owner selects one consequence boundary; paid Gate implementation makes that path preventive.
The first paid wedge
A 90 days $25,000 pilot protects one payer adverse medical-necessity determination workflow. Agent and MCP vendors plus consultancies create distribution leverage. $150K-$250K implementation and $250K-$500K / year operated Gate follow only after the boundary is accepted.
Why this can compound
The Protocol stays open and portable. Models and agent processes change; the customer's mandate, consumption, revocation, uncertainty, and work history survive. Every identity system, policy engine, approval method, agent rail, and evidence source can feed the same neutral boundary instead of being replaced by it.
What the round proves
One paid protected-workflow pilot, one limited-production boundary, independent operation, and repeatable deployment evidence. Public tests and external reproduction are engineering evidence—not customer adoption.
The engineering asset is public and falsifiable. The customer evidence is not yet: EMILIA currently claims no customer traction, recurring revenue, live payer integration, certification, RFC status, or standards-body endorsement. The financing converts software proof into the first external reliance event and repeatable operated deployment.
The technical and narrative investor materials are shared directly. Tell us a little below, or reach us at team@emiliaprotocol.ai.