# Build with Ryde

Connect your applications and AI agents to rides, food, delivery, services and real-world work.

> **Note:** The Ryde Agent Network is in active development. Every capability on this site is marked with its real status, read from the platform's own operation registry — nothing here is described as available before it is. No production credentials are being issued yet.

Ryde runs rides, food and grocery delivery, general shopping, courier and home services on one marketplace. The Agent Network opens that marketplace to software: a REST API, a Model Context Protocol server for AI agents, and OAuth so a customer can connect their own Ryde account to the assistant or platform they already use.

- [Rides](products/rides) — Quote a fare, request a ride, follow the driver.
- [Food](products/food) — Search merchants, read menus, price a basket, place an order.
- [Delivery](products/delivery) — Move a package between two points and track it.
- [Services](products/services) — Find qualified providers and book them into real slots.
- [Tasks](products/tasks) — Dispatch physical-world work with structured evidence.
- [MCP](mcp) — Give an AI agent structured Ryde tools over OAuth.

## How a request is authorized

Four independent questions, and blurring any two of them is how an integration ends up charging someone who never agreed to be charged. Every request through the Agent Network passes all four.

| Layer | Question it answers | Set by |
| --- | --- | --- |
| Authentication | Which application is calling, and for which Ryde customer? | OAuth authorization code + PKCE |
| Authorization | Which capabilities did that customer approve? | Scopes on the access token |
| Entitlement | May this customer transact through an external agent at all? | Ryde One membership / Ryde One Business Agreement |
| Confirmation | Is THIS particular purchase authorized, right now? | A fresh quote the customer was shown, plus an idempotency key |

```
  AI client / application
          |
          |  REST  or  MCP
          v
   RYDE AGENT GATEWAY
          |
   +------+------+------------+
   |             |            |
 Identity   Entitlement    Policy
   |             |            |
 OAuth +      Ryde One    scope, quote,
 grant        active?     idempotency
   |             |            |
   +------+------+------------+
          |
        ALLOWED?
          |
          v
   RYDE DOMAIN SERVICES
   rides · food · delivery · services · tasks
```

> **Info:** MCP is a second face on the same gateway, not a second backend. An agent calling through MCP passes exactly the same identity, scope, entitlement and confirmation checks as an application calling REST — there is no path that skips them.