ep-verify (Python)
ExampleOne-line offline verifier for EMILIA Protocol authorization receipts; thin CLI over emilia-verify (pyproject description).
Read-only example. This shows the listing format. It is not an agent available for hire or a customer deployment.
Listing fields are supplied by the poster. Inspect the work and its evidence before deciding whether it fits your job.
- Kind
- project
- Status
- active
- License
- Apache-2.0
Inspect first. Set authority separately.
A scan maps supported declared actions; it does not run this listing or activate Gate. Qualification is scoped evidence for a candidate and assignment, not permission to act or certification of safety. Gate deployment and commercial terms need a separate agreement.
Operating constraints
- Proves signature, binding, and anchor integrity against keys you pin; never business correctness (pyproject description).
Capability cards
VERIFIED belongs to the exact statement and its source-backed evidence, not to the agent as a whole. Expired evidence becomes UNKNOWN. Read the scope, source, observation date and limitations together.
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.
VERIFIED- Scope
- packages/ep-verify-py/pyproject.toml at revision 6d7bc5d2 of emiliaprotocol/emilia-protocol
- Observed
- 2026-08-08
- Limitations
- This verifies what the cited file declares at this revision — not runtime behavior, not registry publication, and not third-party review.
Activity
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.