Upcar for AI Agents

Search & filter API

The public car-search endpoint is GET /v1/cars/findAvailableCarsNearAddress on https://api.upcar.ai. No API key required. Results are filtered to active, available listings. Cached server-side for 5 minutes (skipped when a price filter is active).

Common parameters:

• latitude, longitude — required, decimal degrees (WGS-84).
• maxDistance — search radius in miles (default 50).
• startDate, endDate — ISO 8601 in UTC. Required for availability filtering.
• priceMin, priceMax — USD per day.
• carType — sedan, suv, truck, van, coupe, convertible, electric.
• limit — page size (default 20, max 1000).

Example request:

GET https://api.upcar.ai/v1/cars/findAvailableCarsNearAddress
  ?latitude=34.0522
  &longitude=-118.2437
  &maxDistance=50
  &startDate=2026-06-15T10:00:00.000Z
  &endDate=2026-06-18T10:00:00.000Z
  &limit=20
  &priceMin=30
  &priceMax=120
  &carType=suv

Example response (truncated):

{
  "data": [
    {
      "_id": "65ab12cd34ef56789abcdef0",
      "make": "Toyota",
      "model": "RAV4",
      "carYear": 2022,
      "carType": "SUV",
      "dailyPrice": 68,
      "averageRating": 4.9,
      "totalRatings": 41,
      "primaryPhotoUrl": "https://images.upcar.ai/...",
      "location": {
        "type": "Point",
        "coordinates": [-118.2437, 34.0522]
      },
      "url": "https://www.upcar.ai/car/65ab12cd34ef56789abcdef0"
    }
  ]
}

Listing detail

Each listing has a canonical URL at https://www.upcar.ai/car/{carId}. The HTML includes server-rendered Schema.org JSON-LD of type Vehicle with a nested Offer (price, currency, availability, businessFunction LeaseOut) plus a BreadcrumbList. Browse the live grid at /search.

JSON detail can be fetched directly via GET /v1/cars/getCar/{carId}. Daily availability is at GET /v1/cars/isCarAvailableForTheseDates/{carId}.

Booking

High-level flow:

1. Search → pick a listing.
2. Trip-quote (price + protection-plan options + delivery fees).
3. Trip-create (reserves the car pending host approval).
4. Stripe payment hold.
5. Host accepts → trip is confirmed.

Public agent-booking API: roadmap. Booking today requires a verified human user account (government ID + face match + Stripe Radar). For now, agent flows must hand off to a human user via OAuth — the human signs in to Upcar once, completes ID verification, then the agent can book on their behalf using the user's session. We're shipping a delegated-agent token model (scoped to a single trip, expiring) — contact us if you want to integrate before public launch.

Identity & verification

Every guest who completes a booking is verified before pickup:

• Government-issued photo ID (driver's license or passport).
• Live face match against the ID via AWS Rekognition (selfie capture).
• Stripe Radar fraud screening on the payment method.
• U.S. driver-history check on the license.

What an agent must hand off: a real human user with a verified ID attached to their Upcar account. We do not allow synthetic or shared identities.

Compliance

Agentic Commerce Protocol (ACP) intent. We're shipping ACP support — delegated tokens, scoped consent, machine- readable purchase intents, and signed receipts. We want to be one of the first marketplaces an ACP-native agent can transact against without scraping. If you're building an agent and want to be a launch partner, email ravi@upcar.ai.

Our /llms.txt, /robots.txt, and sitemap are kept current. Crawlers are welcome on public pages (homepage, /search, /car/{id}, /rent-a-car-in/*). Authenticated routes (account, booking, checkout) are disallowed.

Contact

Agent integrations, ACP partnership, bug reports on this spec: agents@upcar.ai. Founder: ravi@upcar.ai.