〉_ Melega DEX Machine Interface
API & Agents
Reliable data, explicit actions, verifiable outcomes.
API checkingSchema v1
Machine-readable by design
Public read endpoints expose current indexed market and project facts. Write operations remain server-authorized and require their documented confirmation boundary; browser state is never the authority for settlement or fulfilment.
Quickstart for agents
Read the current public market snapshot. No fabricated freshness value is returned.
curl --fail --silent \ -H "Accept: application/json" \ https://www.melega.finance/api/market-data/snapshot/
Schema explorer
GET/api/market-data/snapshot
GET/api/market-data/top-movers
GET/api/indexer/health
GET/api/protocol/activity
GET/api/public/projects/{slug}/machine
Open health response ↗Agent execution contract
An automation must preserve the server-owned amount and receiver, show the proposed operation, receive explicit confirmation, retain an idempotency identity, and verify the final receipt before reporting completion.
Operational confirmation
RequestedExplicit input
ConfirmedHuman or authorized agent
ExecutedCanonical transaction / event
ReconciledIdempotent receipt
Live data contract
Statuschecking
Health checkChecking…
CheckedPending
SourceMelega indexer health
Freshness & provenance
Every consumer should prefer the timestamp, source and status carried by the response. A missing measurement is unavailable, never zero by assumption.
