Skip to content
Menu

DEVELOPER DOCS / CONTRACT 0.101.0

API, CLI and MCP (preview)

One data contract across applications, terminals and AI agents. The MCP server is in preview.

Get started with your AI agent.

Contract snapshot 0.101.0 · Deployment and client release availability follow the integration note for your environment.

One source of permissions and cost

The site, CLI and MCP use the same core API, credentials and approval rules. An agent connection does not bypass scopes or credit review.

Use the supplied client setup

MCP (preview) uses its own address, https://mcp.rewalto.com/mcp. Staging uses https://mcp-dev.rewalto.com/mcp. MCP sign-in stays on these dedicated hosts, independently of the API DNS cutover. Production account sign-in uses Clerk at https://clerk.rewalto.com; staging uses the development Clerk instance. Keep keys private and use the official connection guide. Client-specific installation, OAuth, saved agent connections and connection testing remain unavailable until their integration note is published.

Earlier documentation

Older docs/api quickstart, error, credit and capability documents describe the previous API. Their categories/providers/jobs routes must not be mixed with this core contract. Use the connected environment’s integration note to select the right generation.

Prepare an agent with a clear first task

Give the agent the documentation links, desired dataset and a bounded read-only question. Ask it to explain the available fields, source dates and cost review before proposing execution. Keep tokens out of copied prompts; use the credential mechanism documented for the selected client and environment.

Check setup in three separate steps

First confirm the client can reach the documented service. Then verify identity and permitted capabilities. Finally inspect a small result and its source context. A copied prompt or installed client alone is not evidence of a working, authorised data connection.

Choose an interface for the workflow

Use the API when an application needs structured requests and responses. Use a supplied CLI for terminal work, and a documented MCP integration for supported agents. The interface should preserve the same organisation boundaries, permissions and approval requirements instead of creating a second access path.

Guide: quick commerce MCP server for India

Questions people ask

What is the MCP address?

The MCP server is in preview at https://mcp.rewalto.com/mcp.

Do the API, CLI and MCP have different permissions or costs?

No. They use the same core API, credentials and approval rules. An agent connection does not bypass scopes or credit review.

Can I install a client or save an agent connection today?

Not yet. Client-specific installation, OAuth, saved agent connections and connection testing remain unavailable until their integration note is published.