orcha-sdk
The developer SDK + emerge CLI for Metaorcha —
an orchestration runtime that plans, routes, and executes one goal across agents
speaking MCP, A2A, and COMPUTER_USE (ACP is accepted as an A2A-routed alias).
Register an agent in three lines:
import emerge
@emerge.agent(name="My Agent", description="What I do")
def handle(task: str) -> str:
return f"handled: {task}"
Then serve it:
orcha-sdk run # serve locally + register against the local registry
Install
No clone, no venv setup — just run it:
uvx orcha-sdk init my-agent
Or install it into a project:
pip install orcha-sdk
(Import name is emerge; distribution name is orcha-sdk.)
CLI
| Command | What it does |
|---|---|
orcha-sdk init "My Agent" |
scaffold a new agent from a template |
orcha … |
the same CLI under its short name once installed (uvx --from orcha-sdk orcha init …) |
orcha-sdk run [module] |
serve decorated agents locally + register them against http://localhost:8000 |
orcha-sdk publish [module] --registry <url> |
register against a remote registry |
orcha-sdk verify <envelope.json> |
verify a signed run attestation envelope offline (RFC 0003) |
orcha-sdk run --no-register serves without registering. Set ORCHA_REGISTRY_URL
and ORCHA_PAT to point at and authenticate against a non-local registry.
Verifying run attestations
When the runtime runs with RUN_ATTESTATION_ENABLED, every completed run is
sealed into a signed orcha.run-attestation/v1 envelope (RFC 0003). Anyone
holding the envelope JSON can verify it for free, fully offline:
uvx --from orcha-sdk orcha verify envelope.json # no clone
uvx --from orcha-sdk orcha verify envelope.json --json
orcha-sdk verify envelope.json # after pip/uv install
cat envelope.json | orcha-sdk verify -
Verification recomputes the schema check, the step hash chain (steps_root),
and the Ed25519 signature against the envelope's embedded
signer.public_key_b64 — no network calls, no registry, no DID resolution.
Exit codes: 0 envelope is valid · 1 envelope is invalid (schema, chain, or
signature check failed) · 2 usage/input error (unreadable file, malformed
JSON, unsupported option).
How it works
The decorator records your handler and declared skills. orcha-sdk run serves an
A2A-compatible HTTP endpoint (/health, /.well-known/agent.json, JSON-RPC
message/send / tasks/get) using only the standard library, and uploads a
generated emerge.yaml to the registry. The runtime's planner can then discover
and orchestrate your agent alongside agents that speak other protocols.
Apache 2.0 runtime, MIT SDK. See the main repo.
Metadata
Release files for orcha-sdk 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| orcha_sdk-0.1.3.tar.gz | 24.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| orcha_sdk-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 45.2 kB
Release files / orcha_sdk-0.1.3.tar.gz
| Download URL | orcha_sdk-0.1.3.tar.gz |
|---|---|
| Size | 24.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f85ed9bbd842fcab7bd32ad1418f80e09b84ac2d0caf6228da76187d94d8a779
|
|
BLAKE2b-256 checksum How to use checksums |
d30cb121e6a5d50b8fc07d3049af6149bb853618ed3822a74b579b6aea79af43
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency logRelease files / orcha_sdk-0.1.3-py3-none-any.whl
| Download URL | orcha_sdk-0.1.3-py3-none-any.whl |
|---|---|
| Size | 20.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
24ced1c2bfcb664a976fd8c7e6eccbe60a94358b1b07518970cd62f08effd1d6
|
|
BLAKE2b-256 checksum How to use checksums |
2766de9c6c65871a40c54109e486b2d2185fbd65a71a25f29ca244807245c6fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 12, 2026.
Transparency log