GET STARTED / ELPIS

Documentation

A practical guide to agent spending controls, committed work, evidence, settlement decisions and recoverability.

Start with one job

Give an agent a specific task. Agree on what delivery means. Then evaluate what it submits.

Elpis can record the terms, compare supplied evidence, and produce a replayable decision. You can use that without depositing funds or connecting a wallet.

Begin in the playground, or follow the API quickstart to create a durable job.

The basic idea

1. Commit a condition before work begins
2. Receive evidence
3. Evaluate: release / refund / hold
4. If applicable, separately authorize an escrow transaction

Find what you need

If you need to…	Read
Call Elpis from a service	Developer quickstart
Understand jobs and evidence	Settlement jobs
Use REST, SDKs or MCP	Integrations
Control spending and approvals	Spending rules
Work with escrow and recovery	Recoverability
Review billing and credits	Billing
Understand security boundaries	Security

Three boundaries worth knowing

Permission is not proof of delivery. An allowed payment can still be the wrong payment.
A matching hash is not proof of quality. It confirms a value agrees with the commitment, not who supplied it or whether the work was good.
A decision is not a transfer. A separate authorized transaction and chain receipt are required for an on-chain payment.

Elpis has both a hosted verification API and treasury functionality. The public playground never sends funds. Arc mainnet execution is a separate, higher-risk workflow.

Interfaces

REST is the primary integration path. A scoped MCP endpoint and TypeScript/Python SDK surfaces are available for agents and services. Operators use the web console to review jobs, policies, balances and incidents.

Base URL

https://elpis.devilabs.dev/api/v1

Explore the machine-readable OpenAPI specification for request shapes and errors, or open the API reference.