Shodai Agreements
network.shodai/agreements · v0.1.0 · MCP 2025-11-25
Author, validate, deploy, and operate Shodai on-chain agreements.
Reachability
reachable
checked 2026-07-14 04:35 UTC
Registry status active
Tools pinned 11
520dfbc8f79e
Tools last changed
unchanged since first capture 2026-07-14
Provenance
Registry namespace network.shodai
(domain verified by the official registry)
Repository
github.com/cnslabs/agreements-api-sdk
Remote endpoints
https://shodai.network/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-07-14 03:29 | first capture | 11 tools pinned |
Pinned tool definitions (11)
| Tool | Description |
|---|---|
| list_agreements | Lists agreement summaries visible to the current API key. Supports pagination (cursor + limit), filtering by chain and state, and sorting. Returns summaries only; use get_agreement for the full record. |
| get_agreement | Returns a single agreement record, including the full authored agreement JSON and hosted record context (participants, observers, owner, deployment address). |
| get_agreement_document | Returns the rendered hosted prose document for an agreement by documentId, including content type, display name, chain, docUri, and agreement record references. Use documentId from list_agreements/get_agreement or from... |
| get_agreement_state | Returns the current state of an agreement. For deployed agreements, interpret the state against the states defined in the authored agreement lifecycle (execution.states). Use this to poll for transitions after submitting an input. |
| get_input_history | Returns recorded input submissions for an agreement, with pagination and filtering. Use this to inspect which events have been submitted and whether each is PENDING, MINED, or FAILED. |
| validate_agreement | Checks only the authored agreement JSON document and returns participant variable keys, input IDs, state IDs, and warnings. This does not validate deployment values, participant wallet addresses, signer, or permit data — use... |
| preflight_deployment | Checks whether authored agreement JSON plus target chain, deployment values, participant wallet mappings, and observer context are ready for deployment. This does not deploy the agreement and does not require a signature. Always run... |
| deploy_agreement | Deploys authored agreement JSON using an EIP-712 permit; the API submits the on-chain transaction and returns the deployed agreement record. Provide a pre-signed permit (signer, deadline, signature), or call... |
| submit_input | Submits a signed input to a deployed agreement, advancing its on-chain lifecycle. The input ID and values must match an input defined by the agreement JSON, and the signer must be allowed by that input. Provide a pre-signed permit... |
| prepare_deployment_typed_data | Builds the exact EIP-712 payload that must be signed to authorize deployment of the given agreement JSON. Sign the returned typedData with the deploying wallet (eth_signTypedData_v4 / viem signTypedData), then call deploy_agreement with... |
| prepare_input_typed_data | Builds the exact EIP-712 payload that must be signed to authorize submitting an input to a deployed agreement. Sign the returned typedData with a wallet allowed by the input definition, then call submit_input with signer, deadline, and... |
Status badge
[](https://toolpin.dev/servers/network.shodai/agreements)
Maintain this server? Add the badge to your README — it links your users to this live status page.