# Ride with GPS API (slim)

> Ride with GPS is a cycling route planning and navigation service. Its v1 REST API reads and writes a person's routes, trips, collections and events, uploads GPS files, and runs club member, event, experience and point-of-interest tools for organisation accounts.

- Full: https://www.anchorterminal.com/tools/ride-with-gps.md (~7,250 tokens) · this version ~1,780 tokens · JSON https://www.anchorterminal.com/tools/ride-with-gps.json · canonical https://www.anchorterminal.com/tools/ride-with-gps
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04 · pricing https://www.anchorterminal.com/tools/ride-with-gps#pricing · reviews https://www.anchorterminal.com/tools/ride-with-gps#reviews
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

**E · 45.2/100 · rank #1139 of 1349 · #2 in Hobbies, sport & recreation · not agent-ready · confidence medium**


Assessment: A free, documented REST API with a public OpenAPI file, OAuth, filters and pagination on routes and trips, GPS uploads as polled tasks, and a change log updated five times since August 2026. There is no status page, no rate limit figure, no read-only scope, and the organisation-only endpoints need an account priced by email.

## Facts

- Kind: HTTP API · vendor: Ride with GPS, Inc. · category: Hobbies, sport & recreation · legal entity: Ride with GPS, Inc. · provenance 74/100
- Local only (HTTP)
- Auth: OAuth or key · pricing: Freemium · x402: no · licence: Proprietary service under the Ride with GPS API Terms of Service (effective 11 September 2026)
- Probe metrics: not measured yet (probes haven't run)
- Surface listed: The v1 REST API at https://ridewithgps.com/api/v1, read from the documentation, the OpenAPI file, the authentication and webhooks guides, the API terms, the change log, llms.txt, the general terms and privacy policy, the about, organisations and pricing pages, the App Store listing and the MCP registry on 3 November 2026. No account or API client was created and no request was authenticated
- Endpoints: Users, authentication tokens, collections, events, photos, routes (list, show, create, update, polyline, GPX, TCX, FIT and KML export), trips (the same), sync, tasks, and for organisation accounts club members, experiences (codes, guests, guide pages, messages, packages) and points of interest
- Credentials: api_key per client in x-rwgps-api-key; auth tokens from POST /api/v1/auth_tokens.json (email and password) or the dashboard; OAuth 2.0 authorisation code with scope `user` and a revoke endpoint. No PKCE, expiry or refresh documented
- Formats and pagination: JSON only, with a .json suffix or content-type header. page and page_size (20 to 200) with meta.pagination (record_count, page_count, next_page_url). Filters for name, visibility, distance, elevation gain, archived and stationary
- Errors: 200, 201, 204, 400, 401, 403, 404, 422 and 500 with an `errors` array of strings. No 429 is documented
- Rate limits: None fixed, per the API terms, which ask clients to request only what they need, cache, use webhooks and back off, and say limits may come later
- Webhooks: Configured per API client for route and trip create, update, delete, pin and unpin, signed with HMAC-SHA256 of the body using the client secret. A 200 is expected within 1 second, no retries, redirects not followed
- Plans: Starter free; Basic $9.99 a month or $59.99 a year; Premium $12.99 a month or $79.99 a year with a 7-day trial, per llms.txt and the App Store. Organisation accounts by email
- Legal entity: Ride with GPS, Inc, a Delaware corporation, in the terms of 1 July 2026 under Oregon law; the App Store seller is Ride with GPS LLC. The privacy policy names neither
- Prices: Basic plan $9.99 per month (plan); Premium plan $12.99 per month (plan)

- Scores: Reliability 24, Performance pending, Schema & documentation 72, Agent ergonomics 57, Security & auth 30, Payments & pricing 30, Task success pending, Maintenance & community 60, Transparency & trust 59 · total over the 7 assessed categories
- Why: Reliability, Read with the hosted lines. · Schema & documentation, Public OpenAPI 3.0.1 file with 34 paths, 61 operations and 41 schemas (25). · Agent ergonomics, No field selection; polylines and track files sit on separate endpoints and page_size runs from 20 to 200 (12 of 25). · Security & auth, OAuth 2.0 authorisation code flow with one scope, `user`, and a revoke endpoint, but no PKCE, expiry or refresh token is documented; basic a… · Payments & pricing, Read with the hosted rubric. · Maintenance & community, Read for a closed service. · Transparency & trust, Closed service with API terms effective 11 September 2026 and general terms of 1 July 2026 naming Ride with GPS, Inc under Oregon law; the A…
- Sources: 18, open questions: 6, both in the full twin
- Capabilities: hobbies.routes, hobbies.activities, hobbies.events
- JSON: https://www.anchorterminal.com/api/v1/tools/ride-with-gps.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/ride-with-gps.svg` or a link to https://www.anchorterminal.com/tools/ride-with-gps from a page on ridewithgps.com or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.
- Support: developers@ridewithgps.com; info@ridewithgps.com; organizations@ridewithgps.com; https://support.ridewithgps.com/; https://ridewithgps.com/contact; https://ridewithgps.com/api/v1/doc; more in the full twin

## Before you call it

1. Send x-rwgps-api-key on every request and either x-rwgps-auth-token or `Authorization: Bearer`; ask the person for OAuth consent rather than their password
2. Append .json to endpoints or set `content-type: application/json`, and read the root key named after the resource (`route`, `trip`)
3. Page list endpoints with page and page_size (20 to 200) and stop when meta.pagination.next_page_url is null; add privacy_code for non-public items
4. After POST /api/v1/routes.json with a file, poll GET /api/v1/tasks/{id}.json until the task completes; a package build returns 409 while one is running
5. Treat every delete as final and unconfirmed, since the API has no read-only scope or idempotency key, and back off on failures as the terms ask

## Connect

```bash
curl -H "x-rwgps-api-key: <API_KEY>" -H "x-rwgps-auth-token: <AUTH_TOKEN>" "https://ridewithgps.com/api/v1/routes.json?page_size=20"
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/ride-with-gps

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Strava MCP Connector + API | E | 45.8 | hobbies.activities, hobbies.routes | https://www.anchorterminal.com/tools/strava.min.md |
| Ticketmaster Discovery API | E | 42.9 | hobbies.events | https://www.anchorterminal.com/tools/ticketmaster.min.md |
| Chess.com Published-Data API | E | 40.8 | same category | https://www.anchorterminal.com/tools/chess-com.min.md |
| Rebrickable | F | 34.7 | same category | https://www.anchorterminal.com/tools/rebrickable.min.md |
| Ravelry | F | 16.5 | same category | https://www.anchorterminal.com/tools/ravelry.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)