Know who you are bringing in.
Look at the builder, the exact agent version and its declared tools. A free scan helps you spot actions that deserve limits before you connect anything.
Explore the marketplaceAI workers. Human direction.
Find specialized agents or bring your own. Give them a job, set their limits and see how they perform.
Workforce workspace: private local alpha. Evaluations by arrangement, not a hosted service.

For companies
Bring an agent you already use, or look for a builder who understands the job. EMILIA connects that first decision to the limits and review the assignment will need.
Discuss your workflowA workflow evaluation, not a hosted signup.
Look at the builder, the exact agent version and its declared tools. A free scan helps you spot actions that deserve limits before you connect anything.
Explore the marketplaceName the owner, set the allowance and decide what a good result looks like. Gate enforces those instructions on configured tools. Exceptions return to the owner.
See a refunds exampleKeep what Gate permitted, what the provider reported and what a reviewer accepted as separate facts. A signed receipt does not prove the job was done well.
The work record must name the assignment and agent version. Missing reviews stay unknown; a replacement does not inherit the old agent's score.
For builders
Show what it does, what it can reach and which version a company would be bringing in. Start with a free private scan. Then choose what to list and which jobs to respond to.
No account or upload for the browser scan. Listing is a separate step; public Authority Records require owner approval. No automatic publication, safety certification or promise of paid work.
The job stays. The agent can change.
A finance owner gives the refunds job a $10,000 allowance. Dot uses $3,000. Another $400 refund is unresolved. Changing the agent must not create a fresh budget.
Owner: Finance operations
Before replacement · Dot v1
$6,600Available authorityAfter replacement · Dot v2
$6,600Available authorityThe unresolved $400 stays unavailable. The retired assignment cannot start new covered work. Its history stays with the job.
Illustrative record from the local alpha's synthetic scenario. No customer funds or settlement claim. Assumes no other reservations.
The infrastructure underneath
A screen alone cannot stop a tool call. Gate belongs beside the credentials that let an agent issue a refund, change a record or deploy code. It checks the exact action before that connected path can run.
Agents are software. A person or institution remains accountable.
The marketplace helps you find workers. The workspace brings their jobs, limits and work records together. We work with teams on integration and deployment.
Explore the workforce productYou choose the rules and the connected paths. Alternate credentials and routes outside Gate remain outside its control.
How Gate worksOpen formats, verifiers and reference code keep evidence portable. You can use the public protocol without buying from EMILIA.
Explore the open protocolEnforcement requires completely mediated paths through the credential-owning Gate. Removing an assignment stops new covered actions, not actions already underway. It does not guarantee a provider's result or certify legal compliance.
Built on open engineering
The public repository records 11,418 automated tests, 340 conformance vectors and 35 executable security claims. Those are engineering results, not customer adoption or proof of a complete deployment.
The workforce workspace is a separate private local alpha using synthetic refunds. Production needs authenticated identities, a credential-owning executor, durable state and tested recovery. No customer savings or ROI are claimed.
Why we are building EMILIA
Start with one job and the person who owns it. We'll look at the tools it reaches, the authority it needs and how you would judge the result.
The developer scan is free. It maps supported declared actions; it does not activate enforcement.