Connect an assistant to a buyer's requests.

A buyer can connect ChatGPT to their Ridekick account. The assistant reads their requests and the written prices dealerships sent, each with its state. Only a row whose state is "written" is a dealership's written price. A dealership is not named to a connected assistant until the buyer has unlocked or picked it: every locked row is labelled by its car.

Connect an assistant

1. Add Ridekick's MCP server to the assistant. Its address is https://www.ridekick.com/api/mcp.
2. The assistant sends the buyer to Ridekick to sign in and approve it, with OAuth.
3. The assistant can then list the buyer's requests, and get one request with each dealership's price and its state. Another tool explains how Ridekick works and needs no sign-in.

Use the API directly

One versioned API returns the out-the-door prices from a buyer's own requests, each with its state, lowest written price first within each trim, with a dealership not named to a connected assistant until the buyer has unlocked or picked it (every locked row is labelled by its car). It reads. It does not contact a dealer, accept an offer or complete a purchase.

Quick start

1. Sign in at ridekick.com. Your signed-in session reads your requests and offers. An assistant you approve reads them with its own access token. See Authentication.
2. List your requests, then read one. A request is one ask to several dealers, with the prices that come back. Money is integer cents. The API calls a request a deal set: see /api/v1/deal-sets and dealSetId.
3. Branch on error.code, never on the message. See Errors.

API keys are not available.

For AI coders: every page has a Markdown twin at the same path plus .md. See llms.txt and openapi.json.