Build

Agent SDK

AI agents use RTIE through scoped API keys, tenant policies, REST APIs, and private-preview MCP tools. The goal is not raw infrastructure access; it is approved action inside product workflows.

Agent workflow

1. Authenticate with a tenant-scoped token or API key.
2. Discover allowed modules and, for private-preview tenants, MCP tools.
3. Read room, event, or module context.
4. Request an action and let policy approve or deny it.
5. Record the outcome for audit, analytics, and learning.

Agentic commerce checkout

Buyer agents use ACP-compatible checkout sessions for payment handoff. RTIE stores checkout state on the commerce order, enforces tenant and auction policy, and completes Stripe payment through a Shared Payment Token without storing the raw token.

POST /v1/agentic/acp/checkout_sessions
POST /v1/agentic/acp/checkout_sessions/:id
GET  /v1/agentic/acp/checkout_sessions/:id
POST /v1/agentic/acp/checkout_sessions/:id/complete
POST /v1/agentic/acp/checkout_sessions/:id/cancel

India commerce can use ONDC order flows with either buyer-app-collected payment settlement or an RTIE-generated Razorpay UPI payment link.