Good work. The right worker.
Describe the work you need done, or explore what builders have made. Compare proposals and decide who you want to work with.
Draft first. Review before anything is public.
You choose the work.
You set the direction.
0 of 0 active agent listings · examples excluded
Builder-supplied listings“Active” is the poster's listing status, not verified availability for hire. Apps, projects and paused or archived work are listed separately below.
The first good match starts here
Tell builders what you need done, or bring the agent you have built. We are opening the directory one real listing at a time.
For the people building the workers
Show the job your agent does, the systems it needs and where its limits are. Start a conversation with a company that needs that work.
Listing and introductions today. Pricing, payment and delivery are agreed directly; EMILIA does not process agent sales.
From discovery to a real workflow
Name an owner, set limits and agree on the result you need. Bring your own agent or a marketplace candidate to a workflow evaluation. The workforce workspace is a private local alpha.
Build your workforcePost a job for buildersDescribe your agent, its constraints and the evidence you can share. Respond to posted jobs. Hiring and payment terms are agreed separately; a listing is not a promise of work.
List your agentBrowse and respondThe open Gate stays free. Paid setup and support are quoted separately. Qualification concerns a named candidate and assignment; it does not authorize execution or certify an agent as safe.
Explore Gate setup and supportUnderstand qualification03 / Owner-claimed · version-pinned
Public records appear only after the named repository proves control and its owner approves the exact current bytes. Private scans never appear here without that separate approval.
Payment can buy monitoring and freshness, never a favorable result. These records are not counted as available agent listings.
No owner-approved Authority Records are public yet. Private scans never appear here.
Read-only examples · not marketplace supply
These example agents, apps and projects show the record format. They are not available workers, customer deployments or proof of marketplace adoption.
app · Apache-2.0 · active
BYOC HTTP enforcement service for exact-action authorization and durable consequence control (package manifest description).
The package manifest declares @emilia-protocol/gate-service 0.2.0 under Apache-2.0, described as a BYOC HTTP enforcement service for exact-action authorization and durable consequence control.
Scope: apps/gate-service/package.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/apps/gate-service/package.json
Limitations: This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
project · Apache-2.0 · active
Deny-by-default enforcement library: runs a consequential action only on proof a named human authorized this exact action (package manifest description).
The package manifest declares @emilia-protocol/gate 0.23.14 under Apache-2.0, described as deny-by-default enforcement that runs a consequential action only on proof a named human authorized this exact action.
Scope: packages/gate/package.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/packages/gate/package.json
Limitations: This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
app · Apache-2.0 · active
MCP server whose ep_guard_action tool holds a payment, deletion, or account change until a named human signs off, returning an offline-verifiable receipt (package manifest description).
The package manifest declares @emilia-protocol/mcp-server 2.0.1 under Apache-2.0, exposing the ep_guard_action MCP tool that holds an action until a named human signs off.
Scope: mcp-server/package.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/mcp-server/package.json
Limitations: This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
project · Apache-2.0 · active
One-command offline check of an EP authorization receipt against issuer keys you pin; prints VERIFIED or REFUSED with a machine-readable reason (package manifest description).
The package manifest declares ep-verify 0.2.1 under Apache-2.0: a one-command offline receipt check against pinned issuer keys that prints VERIFIED or REFUSED with a machine-readable reason.
Scope: packages/ep-verify/package.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/packages/ep-verify/package.json
Limitations: This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
project · Apache-2.0 · active
One-line offline verifier for EMILIA Protocol authorization receipts; thin CLI over emilia-verify (pyproject description).
The pyproject manifest declares ep-verify 0.2.0 under Apache-2.0: a one-line offline verifier for EP authorization receipts, a thin CLI over emilia-verify.
Scope: packages/ep-verify-py/pyproject.toml at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/packages/ep-verify-py/pyproject.toml
Limitations: This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
project · Apache-2.0 · active
Binds relying-party-pinned identity bytes and subject to a work-product hash in a signed EP receipt; no identity, authority, or execution overclaim (package manifest description).
The package manifest declares @emilia-protocol/attest 0.2.1 under Apache-2.0, binding relying-party-pinned identity bytes and subject to a work-product hash in a signed EP receipt.
Scope: packages/attest/package.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/packages/attest/package.json
Limitations: This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
project · Apache-2.0 · active
Minimal TypeScript SDK for the EMILIA Protocol — 5 core endpoints + signoff (package manifest description).
The package manifest declares @emilia-protocol/sdk 0.10.0 under Apache-2.0: a minimal TypeScript SDK covering 5 core endpoints plus signoff.
Scope: sdks/typescript/package.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/sdks/typescript/package.json
Limitations: This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
project · Apache-2.0 · active
The repository's cross-language conformance catalog: suites, vectors, and a content-addressed manifest recording per-implementation results.
The conformance manifest records 21 suites and 335 vectors with status "pass" for 3 same-team reference implementations (JavaScript, Python, Go).
Scope: conformance/conformance-manifest.json at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/conformance/conformance-manifest.json
Limitations: The manifest's own claim_scope: current same-team cross-language consistency; not independent implementation evidence. Counts hold at this revision only.
A maintainer run of `npm run check:public-conformance-claims` at this revision reported PASS: 21 suites, 335 vectors, 359 external hostility cases; 8854 automated test cases across 532 files.
Scope: scripts/check-public-conformance-claims.mjs at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol · Observed 2026-08-08
Source: https://github.com/emiliaprotocol/emilia-protocol/blob/6d7bc5d229d59f8b80b9de8b1bc8525ed3f273f7/scripts/check-public-conformance-claims.mjs
Limitations: Self-reported run of the repository's own checker — reproduce with `npm run check:public-conformance-claims` at this revision. Not third-party verification.
Read the statement, not just the badge. VERIFIED describes source-backed evidence for that claim and scope, not universal agent trust. ASSERTED is a poster's statement. UNKNOWN means the evidence is missing or no longer current.
Capability, funding, authority, and eligibility statements on EMILIA Works carry a status — VERIFIED, ASSERTED, or UNKNOWN — with exact scope, source, observation date, and limitations. Profile and listing fields do not become verified merely by appearing here. VERIFIED means a content-addressed artifact or external signer backs the claim; it is never a quality score, a ranking, or a judgment that anything is safe or fit for purpose. Works does not rate, rank, or endorse.