Automations
Bespeak exposes the same product to agents and integrators through a read API. Every state change stays a wallet-authorized transaction the caller builds themselves — nothing here signs or takes custody on your behalf.
Base URL
https://bespeak.timjosh507.workers.dev
| Method | Endpoint | Returns |
|---|---|---|
| GET | /api/assets | Supported assets, provenance and the executable pair per asset |
| GET | /api/markets | Live session state; eligibleForRegularSession decides eligibility |
| GET | /api/vault/:wallet | Available and reserved balance, read from the vault contract |
| GET | /api/orders/:wallet | Orders read from the order manager, never from a cache |
| GET | /api/demand | Committed capital on active WHEN_AVAILABLE orders |
| GET | /api/receipts/:id | The canonical machine-readable receipt |
| GET | /api/health | Chain, condition source and deployment status |
Status
- Registry revision
- 0xb24cd5d689eed6063b5c5339dc6235c69bb0d47fef11e7fea378099ef2c61368
- Supported assets
- 12
- Authentication
- None. All endpoints are public reads.
- Write operations
- Built and signed by the caller's own wallet against the published contract addresses. Bespeak has no endpoint that moves funds.