{ "data": { "a": { "slug": "ride-with-gps", "name": "Ride with GPS API", "vendor": "Ride with GPS, Inc.", "vendorUrl": "https://ridewithgps.com", "kind": "http-api", "category": "hobbies", "summary": "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.", "url": "https://www.anchorterminal.com/tools/ride-with-gps", "markdownUrl": "https://www.anchorterminal.com/tools/ride-with-gps.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ride-with-gps.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ride-with-gps.json", "dns": "ride-with-gps.grade.anchorterminal.com", "license": "Proprietary service under the Ride with GPS API Terms of Service (effective 11 September 2026)", "transports": [ "http" ], "packages": [], "auth": "mixed", "authNotes": "An API client, created on the API clients page after a browser signup, gives an api_key sent as x-rwgps-api-key. OAuth 2.0 authorisation code flow (https://ridewithgps.com/oauth/authorize, token at /oauth/token.json, revoke at /oauth/revoke.json) returns a Bearer token with scope `user`; no PKCE, expiry or refresh token is documented. Basic auth uses an auth token minted from the account email and password at POST /api/v1/auth_tokens.json, or created in the dashboard for organisation accounts, with no documented expiry or revocation (https://ridewithgps.com/api/v1/doc/authentication).", "pricing": "freemium", "pricingNotes": "The API is free with no paid plan or approval, per the API terms. A free Starter account suffices for a client. Basic ($9.99 a month or $59.99 a year) and Premium ($12.99 a month or $79.99 a year, 7-day trial) per ridewithgps.com/llms.txt and the App Store listing; the pricing page shows the tiers without figures to our reader. Organisation accounts, which the member, event, experience and point-of-interest endpoints need, are priced by email to organizations@ridewithgps.com.", "priceSummary": "$9.99 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, OpenAPI file, API terms or llms.txt (checked 3 November 2026).", "endpoints": [] }, "toolCount": 0, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://ridewithgps.com/api/v1/doc", "llmsTxt": "https://ridewithgps.com/llms.txt", "openapi": "https://ridewithgps.com/api/v1/openapi.yaml", "capabilities": [ "hobbies.routes", "hobbies.activities", "hobbies.events" ], "tags": [ "hosted", "oauth", "api-key", "openapi", "llms-txt", "free-tier", "no-card", "webhooks", "closed-source", "cycling" ], "lastRelease": "2026-10-14", "graded": true, "anchor": { "graded": true, "score": 45.2, "grade": "E", "agentReady": false, "rank": 1139, "ranked": true, "rankOf": 1349, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 60, "payments": 30, "reliability": 24, "schema": 72, "security": 30, "transparency": 59 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "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.", "bestFor": "An agent planning or reading cycling routes and rides for a consenting person, or running a club's calendar from an organisation account.", "strengths": [ "Public OpenAPI 3.0.1 file with 34 paths and 61 operations, plus an llms.txt that states the plans and prices", "API terms of 11 September 2026 allow commercial use with no fee, approval or attribution", "Routes and trips can be created from GPX, TCX, FIT or KML uploads and exported in the same formats, with page_size up to 200 and distance, elevation, visibility and archived filters", "HMAC-SHA256 signed webhooks for route and trip changes, with a 100-notification batch and item URLs to fetch", "Change log entries on 10 August, 3 September, 11 September, 6 October and 14 October 2026" ], "weaknesses": [ "No status page or incident history; status.ridewithgps.com redirects to the home page", "No rate limit figures, no 429 documented, and no idempotency keys on the 30 write operations", "OAuth has a single `user` scope with no read-only option, no PKCE and no documented token expiry; basic auth tokens come from the account password", "The 23 March 2026 change to route activity_types was breaking, with a migration map but no notice period", "Member, event, experience and point-of-interest endpoints need an organisation account priced by email" ], "agentNotes": [ "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", "Append .json to endpoints or set `content-type: application/json`, and read the root key named after the resource (`route`, `trip`)", "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", "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", "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" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 45.2 } ], "editorialScores": { "ergonomics": 57, "maintenance": 60, "payments": 30, "reliability": 24, "schema": 72, "security": 30, "transparency": 43 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"x-rwgps-api-key: \u003cAPI_KEY\u003e\" -H \"x-rwgps-auth-token: \u003cAUTH_TOKEN\u003e\" \"https://ridewithgps.com/api/v1/routes.json?page_size=20\"" }, "letme": { "capability": "https://letme.dev/hobbies.routes", "tool": "https://letme.dev/ride-with-gps" }, "area": "everyday", "unitPrices": [ { "item": "Basic plan", "unit": "month", "usd": 9.99, "note": "$59.99 a year; the API itself is free" }, { "item": "Premium plan", "unit": "month", "usd": 12.99, "note": "$79.99 a year, 7-day trial" } ], "provenance": { "legalEntity": "Ride with GPS, Inc.", "domain": "ridewithgps.com", "domainRegistered": "2007-04-16", "endpointOnVendorDomain": true, "terms": "https://ridewithgps.com/api/v1/doc/terms", "privacy": "https://ridewithgps.com/privacy", "statusPage": "", "changelog": "https://ridewithgps.com/api/v1/doc/change_log", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "Ride with GPS, Inc, a Delaware corporation, is named in the terms of service effective 1 July 2026. The App Store lists the seller as Ride with GPS LLC. The privacy policy (last updated 31 July 2026) names no entity.", "API Terms of Service effective 11 September 2026 supplement the general terms. Neither forbids automated access; the API terms ask for responsible traffic and say unusual traffic should be discussed first.", "ridewithgps.com/robots.txt disallows raw track exports, route and trip JSON, cue sheets, elevation profiles and images for every agent, none of which was fetched; the API documentation paths are allowed. changelog.ridewithgps.com allows all. support.ridewithgps.com answered 403.", "status.ridewithgps.com answers 301 to the home page. /.well-known/security.txt returns 404.", "RDAP (Verisign) gives ridewithgps.com a creation date of 16 April 2007." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ride-with-gps.json", "live": { "slug": "ride-with-gps", "securityTxt": { "url": "https://ridewithgps.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:43.62212682Z" }, "updatedAt": "2026-11-04T15:54:43.62212682Z" } }, "answer": "Ride with GPS API scores 45.2 (E) on agent readiness against Ticketmaster Discovery API's 42.9 (E), and leads in 3 of 7 scored categories. Ticketmaster Discovery API leads on reliability, agent ergonomics and transparency \u0026 trust.", "b": { "slug": "ticketmaster", "name": "Ticketmaster Discovery API", "vendor": "Ticketmaster (Live Nation Entertainment)", "vendorUrl": "https://developer.ticketmaster.com", "kind": "http-api", "category": "hobbies", "summary": "Ticketmaster's Discovery API searches events, attractions, venues and classifications across Ticketmaster, Universe, FrontGate and Ticketmaster Resale, with a key from the developer portal. Buying tickets needs the Partner API, which is open only to approved distribution partners.", "url": "https://www.anchorterminal.com/tools/ticketmaster", "markdownUrl": "https://www.anchorterminal.com/tools/ticketmaster.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/ticketmaster.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/ticketmaster.json", "dns": "ticketmaster.grade.anchorterminal.com", "repo": "https://github.com/ticketmaster-api", "license": "Proprietary service. Developer portal General Terms of Use last updated 27 June 2023; privacy policy last updated 29 July 2026", "transports": [], "packages": [], "auth": "api-key", "authNotes": "One API key per application, registered in the developer portal after a browser signup, sent as the `apikey` query parameter on every request. The Partner API also accepts an `x-api-key` header. No scopes, expiry or rotation documented. A missing or invalid key returns 401 with errorcode oauth.v2.InvalidApiKey.", "pricing": "free", "pricingNotes": "The Discovery API and Discovery Feed are free with a developer account, 5,000 calls a day and 5 a second by default (the FAQ says 2 a second). Higher limits are granted case by case. The terms forbid deriving revenue from use of the API; affiliates earn commission on sales through the Impact programme at rates set during onboarding. The Partner API is for approved distribution partners.", "priceSummary": "Free", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Discovery API docs, getting started, FAQ or terms (checked 2026-11-03).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://developer.ticketmaster.com/products-and-docs/apis/discovery-api/v2/", "capabilities": [ "hobbies.events" ], "tags": [ "hosted", "closed-source", "api-key", "free", "free-tier", "no-card", "partner-only" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 42.9, "grade": "E", "agentReady": false, "rank": 1176, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 48, "payments": 30, "reliability": 45, "schema": 42, "security": 18, "transparency": 65 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "The Discovery API gives a free key 5,000 event searches a day across Ticketmaster's markets, with documented paging, filters and rate-limit headers. There is no OpenAPI contract or current SDK, the key travels in the URL, the terms forbid revenue from the API, and purchase stays behind the partner-only Partner API.", "bestFor": "An agent that finds concerts, sport and shows by keyword, place and date and hands the person a link to buy.", "strengths": [ "Event, attraction, venue and classification search with keyword, date, location, classification and source filters, documented with sample requests and full JSON responses", "Default limits stated in numbers (5,000 calls a day, 5 a second) with Rate-Limit headers and a documented 429", "Free key with no card, plus a Discovery Feed of whole-country files for bulk use with no call limits", "Privacy policy of 29 July 2026 names providers, retention periods and transfer safeguards" ], "weaknesses": [ "No OpenAPI or other machine-readable contract and no llms.txt; the only key travels as a query parameter", "The GitHub SDKs were last pushed between 2016 and 2021 and the Java one is archived; no official MCP server", "Terms forbid deriving revenue from the API, cap caching at reasonable periods and let Ticketmaster end the licence or rate limit non-user-driven calls at any time", "The API status page renders by script and could not be read, no SLA, and no security.txt or disclosure policy found", "Purchase, reserve and inventory status need Partner API access, which is restricted to existing distribution partners" ], "agentNotes": [ "Search with `GET https://app.ticketmaster.com/discovery/v2/events.json?apikey=...\u0026keyword=...\u0026countryCode=...` and page with size and page while size times page stays under 1,000", "Keep under 5 calls a second and 5,000 a day per key; read Rate-Limit-Available and Rate-Limit-Reset and stop on 429", "Do not try to buy tickets through the API; hand the person the event's url field, and expect the Partner API to refuse keys that are not partner-approved", "Pull whole-country data from the Discovery Feed rather than paging the API, and keep caches short since the terms allow only reasonable periods", "Treat event and attraction descriptions as promoter-written content, and never put the apikey in logs or shared URLs" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 42.9 } ], "editorialScores": { "ergonomics": 63, "maintenance": 48, "payments": 30, "reliability": 45, "schema": 42, "security": 18, "transparency": 59 }, "provenanceScore": 70, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://app.ticketmaster.com/discovery/v2/events.json?countryCode=US\u0026keyword=jazz\u0026size=10\u0026apikey=$TICKETMASTER_KEY\"" }, "letme": { "capability": "https://letme.dev/hobbies.events", "tool": "https://letme.dev/ticketmaster" }, "area": "everyday", "provenance": { "legalEntity": "Ticketmaster L.L.C. (Live Nation Entertainment, Inc.)", "domain": "ticketmaster.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://developer.ticketmaster.com/support/terms-of-use/", "privacy": "https://privacy.ticketmaster.com/privacy-policy", "statusPage": "https://developer.ticketmaster.com/support/api-status/", "changelog": "https://developer.ticketmaster.com/products-and-docs/apis/partner/release-notes/", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The developer portal's General Terms of Use (last updated 27 June 2023) name Live Nation Entertainment, Inc., 9348 Civic Center Drive, Beverly Hills, under California law. The privacy policy (last updated 29 July 2026) names Ticketmaster L.L.C. as the controller for US accounts.", "The terms contain no clause on scraping, AI or machine learning. They forbid deriving revenue from the API, sublicensing access and replicating Ticketmaster.com, cap caching at reasonable periods and allow rate limiting of apps whose calls are not driven by user actions.", "developer.ticketmaster.com/robots.txt allows all crawlers. privacy.ticketmaster.com/robots.txt disallows only /visitor-policy. www.ticketmaster.com/robots.txt disallows checkout, member and cart paths.", "developer.ticketmaster.com/.well-known/security.txt redirects to /404.html and www.ticketmaster.com/.well-known/security.txt answers 404 with the browse page.", "The API status page at /support/api-status/ needs JavaScript and showed no status or history to our reader. The newest dated release notes on the portal are the Partner API's (16 October 2026); no Discovery API changelog was found on the live portal, and the one in the ticketmaster-api.github.io repository ends in June 2016." ], "score": 70 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/ticketmaster.json", "live": { "slug": "ticketmaster", "vendorStatus": { "page": "https://developer.ticketmaster.com/support/api-status", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:32:39.189683347Z" }, "securityTxt": { "url": "https://ticketmaster.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:54:41.891848031Z" }, "updatedAt": "2026-11-04T15:54:41.891848031Z" } }, "edges": [ { "by": 30, "category": "schema", "leads": "ride-with-gps", "name": "Schema \u0026 documentation", "reasons": { "a": "Public OpenAPI 3.0.1 file with 34 paths, 61 operations and 41 schemas (25). ridewithgps.com/llms.txt describes the product and plans but links no Markdown docs, and the documentation is HTML (5 of 10). Operation descriptions say which endpoints are organisation-only, that uploads and package builds return a task to poll, how experience codes replace each other and that deleting a member keeps their account; little on when not to use an operation (14 of 20). 18 enums, required fields and defaults in the file, but the Error schema is an array of strings (10 of 15). One example in the OpenAPI file, request and pagination examples on the docs pages, and a table of HTTP codes with the `errors` array shape (8 of 15). One version in the path, a rule that only incompatible changes create a new version, and a dated change log back to January 2025 (15). 25 + 5 + 14 + 10 + 8 + 15 = 72.", "b": "No OpenAPI or other machine-readable contract found; the API Explorer is interactive only (0 of 25). No llms.txt or Markdown docs (0). Each endpoint is documented with its purpose, parameters and defaults, but nothing says when not to use one (12 of 20). Typed parameters with enums (includeTest yes, no, only; includeSpellcheck; sort keys; source) and defaults, with required fields limited to the key (12 of 15). Sample requests and full JSON responses for each endpoint, but the only documented error is the 401 for a bad key, with no error catalogue for Discovery (10 of 15). v2 in the path, Partner and Inventory Status release notes with dates, but no changelog for the Discovery API on the live portal (8 of 15). Total 42." }, "scores": { "a": 72, "b": 42 } }, { "by": 21, "category": "reliability", "leads": "ticketmaster", "name": "Reliability", "reasons": { "a": "Read with the hosted lines. No status page, since status.ridewithgps.com answers 301 to the home page and the docs link none (0). No readable incident history (5). The API terms of 11 September 2026 say no fixed request limits currently apply and ask for caching, webhooks and backing off, so there are no numbers to publish (5 of 15). No 429 is documented in the docs or the OpenAPI file; the terms ask clients to back off on failures, uploads run as tasks to poll, and no idempotency key exists for the 30 write operations (4 of 15). No SLA (0). v1 is the current and only version with no beta label (10). 0 + 5 + 5 + 4 + 0 + 10 = 24.", "b": "Read with the hosted lines. The portal has an API status page at /support/api-status/, but it renders by script and showed no components or history to our reader, so the line is part met (5 of 20). No readable incident history (5). Default limits stated in numbers, 5,000 calls a day and 5 a second on the getting started page, 2 a second in the FAQ (15). 429 over quota with Rate-Limit-Over and Rate-Limit-Reset headers, no Retry-After or backoff guidance, and the graded surface only reads (10 of 15). No SLA found (0). Discovery v2 has been general since January 2016 (10). Total 45." }, "scores": { "a": 24, "b": 45 } }, { "by": 12, "category": "security", "leads": "ride-with-gps", "name": "Security \u0026 auth", "reasons": { "a": "OAuth 2.0 authorisation code flow with one scope, `user`, and a revoke endpoint, but no PKCE, expiry or refresh token is documented; basic auth tokens are minted from the account email and password with no documented expiry or revocation; credentials travel in headers (18 of 30). No read-only scope, and the 30 write operations, including deletes of routes, events, members and experiences, need no confirmation (4 of 20). Route names, descriptions, event text and experience messages are user content with no guidance on treating them as untrusted (5 of 15). The API clients page lists clients and tokens; no call log is documented (3 of 15). /.well-known/security.txt returns 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 18 + 4 + 5 + 3 + 0 = 30.", "b": "One key per app with no scopes, sent as the apikey query parameter as the documented route, so 10 less 10 (0 of 30). The open key reaches only the read-only Discovery surface; reserve and purchase need partner approval (10 of 20). Event and attraction descriptions are promoter-written content, with no injection guidance (5 of 15). Rate-limit headers give per-call usage, no audit log (3 of 15). No security.txt (404 on both hosts), no disclosure policy, bug bounty or certification found on the portal (0 of 20). Total 18." }, "scores": { "a": 30, "b": 18 } }, { "by": 12, "category": "maintenance", "leads": "ride-with-gps", "name": "Maintenance \u0026 community", "reasons": { "a": "Read for a closed service. The newest change log entry is 14 October 2026 (30). Five dated entries since 4 August 2026, on 10 August, 3 September, 11 September, 6 October and 14 October (20). A dated change log, developers@ridewithgps.com and a Zendesk help centre that answered 403 to our reader; replies were not tested (10 of 15). No official SDK and no entry in the official MCP registry (0 of 15). No package or CI to judge (0 of 10). 30 + 20 + 10 + 0 + 0 = 60.", "b": "Read for a closed service. The newest dated API change on the portal is the Partner API release note of 16 October 2026; none was found for the Discovery API itself, so the line is part met (20 of 30). Partner API notes dated 4, 11, 19 and 31 August and 16 October 2026 make three in 90 days (20). A developer support form with replies by email, a 48-hour promise for affiliate questions, and no public forum (8 of 15). The GitHub SDKs were last pushed between 2016 and 2021, the Java one is archived, and there is no entry in the MCP registry (0 of 15). The SDK repositories are stale (0 of 10). Total 48." }, "scores": { "a": 60, "b": 48 } }, { "by": 6, "category": "ergonomics", "leads": "ticketmaster", "name": "Agent ergonomics", "reasons": { "a": "No field selection; polylines and track files sit on separate endpoints and page_size runs from 20 to 200 (12 of 25). page and page_size with meta.pagination, filters for name, visibility, distance, elevation gain, archived and stationary, and privacy_code for non-public items (20). Errors carry HTTP codes and an `errors` array of messages with no codes to branch on (10 of 20). Reads are safe to repeat and package builds return 409 while one runs, but no idempotency key covers creates, and deletes are not confirmed (8 of 20). Two headers and a .json suffix are all a request needs, with no official SDK (7 of 15). 12 + 20 + 10 + 8 + 7 = 57.", "b": "Pages of up to 200 events by size, but no field selection, and each event carries nested dates, sales, classifications, images, price ranges, promoter, venue and links (12 of 25). Paging by size and page with the 1,000-item depth limit, keyword, date, location, radius, classification, source and locale filters, and sort keys (18 of 20). 401 carries a faultstring and errorcode, 429 has headers, but no other error body is documented for Discovery (10 of 20). The surface is read-only and safe to retry (15 of 20). One required parameter, sensible defaults, but no current official SDK; the GitHub SDKs date from 2016 to 2021 (8 of 15). Total 63." }, "scores": { "a": 57, "b": 63 } }, { "by": 6, "category": "transparency", "leads": "ticketmaster", "name": "Transparency \u0026 trust", "reasons": { "a": "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 App Store names Ride with GPS LLC (15 of 30). The privacy policy of 31 July 2026 gives no fixed retention periods, names Google Maps, Google and Apple and other providers only by category, and names no entity (12 of 30). The API terms promise reasonable advance notice of material changes through the change log or email, and the 23 March 2026 breaking change to activity_types shipped with a migration map and no notice window (10 of 20). Processing in the United States and other jurisdictions with safeguards where required; no subprocessor list (6 of 20). 15 + 12 + 10 + 6 = 43.", "b": "Closed service with clear terms naming Live Nation Entertainment, Inc. under California law, last updated 27 June 2023 (15 of 30). The privacy policy of 29 July 2026 names the controller, retention (deletion within 90 days of a request, 7 years of inactivity, longer for tax records) and providers, and agrees with itself; no DPA for developers (22 of 30). Deprecations are announced (the XML feed, the International Discovery API folding into Discovery, null price fields) without notice periods (8 of 20). Providers named (Braintree, Zendesk, Concentrix, Salesforce, Ekata, OneTrust, Forter) with the platform run from the United States and United Kingdom and Standard Contractual Clauses for transfers (14 of 20). Total 59." }, "scores": { "a": 59, "b": 65 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Ride with GPS, Inc.", "b": "Ticketmaster (Live Nation Entertainment)", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Ride with GPS API Terms of Service (effective 11 September 2026)", "b": "Proprietary service. Developer portal General Terms of Use last updated 27 June 2023; privacy policy last updated 29 July 2026", "name": "Licence" }, { "a": "0", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "2026-10-14", "b": "2026-10-16", "name": "Last release" }, { "a": "2026-09-11", "b": "2023-06-27", "name": "Terms last updated" }, { "a": "2026-07-31", "b": "2026-07-29", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Ride with GPS API scores 45.2 (E) on agent readiness against Ticketmaster Discovery API's 42.9 (E), and leads in 3 of 7 scored categories. Ticketmaster Discovery API leads on reliability, agent ergonomics and transparency \u0026 trust.", "question": "Which is better for AI agents, Ride with GPS API or Ticketmaster Discovery API?" }, { "answer": "Ride with GPS API takes an API key or an OAuth sign-in. Ticketmaster Discovery API needs an API key.", "question": "Do Ride with GPS API and Ticketmaster Discovery API need an API key?" }, { "answer": "No hosted endpoint is listed for Ride with GPS API. No hosted endpoint is listed for Ticketmaster Discovery API.", "question": "Can an agent call Ride with GPS API and Ticketmaster Discovery API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 72 against 42", "Security \u0026 auth, 30 against 18", "Maintenance \u0026 community, 60 against 48" ], "also": null, "goodFor": "An agent planning or reading cycling routes and rides for a consenting person, or running a club's calendar from an organisation account.", "slug": "ride-with-gps", "watchFor": "No status page or incident history; status.ridewithgps.com redirects to the home page" }, { "aheadOn": [ "Reliability, 45 against 24", "Agent ergonomics, 63 against 57", "Transparency \u0026 trust, 65 against 59" ], "also": null, "goodFor": "An agent that finds concerts, sport and shows by keyword, place and date and hands the person a link to buy.", "slug": "ticketmaster", "watchFor": "No OpenAPI or other machine-readable contract and no llms.txt; the only key travels as a query parameter" } ], "history": null, "job": { "capability": "hobbies.events", "name": "Hobbies events" }, "others": [ { "json": "https://www.anchorterminal.com/compare/ride-with-gps-vs-strava.json", "title": "Ride with GPS API vs Strava MCP Connector + API", "url": "https://www.anchorterminal.com/compare/ride-with-gps-vs-strava" } ], "panel": null, "scores": [ { "by": 21, "edge": "ticketmaster", "key": "reliability", "name": "Reliability", "ride-with-gps": 24, "ticketmaster": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 30, "edge": "ride-with-gps", "key": "schema", "name": "Schema \u0026 documentation", "ride-with-gps": 72, "ticketmaster": 42, "weight": 13 }, { "by": 6, "edge": "ticketmaster", "key": "ergonomics", "name": "Agent ergonomics", "ride-with-gps": 57, "ticketmaster": 63, "weight": 13 }, { "by": 12, "edge": "ride-with-gps", "key": "security", "name": "Security \u0026 auth", "ride-with-gps": 30, "ticketmaster": 18, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "ride-with-gps": 30, "ticketmaster": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "edge": "ride-with-gps", "key": "maintenance", "name": "Maintenance \u0026 community", "ride-with-gps": 60, "ticketmaster": 48, "weight": 7 }, { "by": 6, "edge": "ticketmaster", "key": "transparency", "name": "Transparency \u0026 trust", "ride-with-gps": 59, "ticketmaster": 65, "weight": 7 } ], "summary": "Ride with GPS API scores 45.2 (E) on agent readiness against Ticketmaster Discovery API's 42.9 (E), and leads in 3 of 7 scored categories. Ticketmaster Discovery API leads on reliability, agent ergonomics and transparency \u0026 trust. Both do hobbies events.", "tasks": null, "tutorials": [], "verdicts": { "ride-with-gps": "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.", "ticketmaster": "The Discovery API gives a free key 5,000 event searches a day across Ticketmaster's markets, with documented paging, filters and rate-limit headers. There is no OpenAPI contract or current SDK, the key travels in the URL, the terms forbid revenue from the API, and purchase stays behind the partner-only Partner API." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster", "json": "https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster.min.md" }, "markdown": "Ride with GPS API scores 45.2 (E) on agent readiness against Ticketmaster Discovery API's 42.9 (E), and leads in 3 of 7 scored categories. Ticketmaster Discovery API leads on reliability, agent ergonomics and transparency \u0026 trust. Both do hobbies events.\n\n- Ride with GPS API: grade E, 45.2/100, rank #1139 of 1349. Markdown https://www.anchorterminal.com/tools/ride-with-gps.md · JSON https://www.anchorterminal.com/api/v1/tools/ride-with-gps.json\n- Ticketmaster Discovery API: grade E, 42.9/100, rank #1176 of 1349. Markdown https://www.anchorterminal.com/tools/ticketmaster.md · JSON https://www.anchorterminal.com/api/v1/tools/ticketmaster.json\n- Best hobby, sport and recreation APIs for AI agents: https://www.anchorterminal.com/best/hobbies/index.md\n- All 3 hobbies comparisons: https://www.anchorterminal.com/compare/hobbies/index.md\n\n## Which one, for what\n\n### Ride with GPS API (E)\n\nGood for: An agent planning or reading cycling routes and rides for a consenting person, or running a club's calendar from an organisation account.\n\nAhead on:\n- Schema \u0026 documentation, 72 against 42\n- Security \u0026 auth, 30 against 18\n- Maintenance \u0026 community, 60 against 48\n\nWatch for: No status page or incident history; status.ridewithgps.com redirects to the home page\n\n### Ticketmaster Discovery API (E)\n\nGood for: An agent that finds concerts, sport and shows by keyword, place and date and hands the person a link to buy.\n\nAhead on:\n- Reliability, 45 against 24\n- Agent ergonomics, 63 against 57\n- Transparency \u0026 trust, 65 against 59\n\nWatch for: No OpenAPI or other machine-readable contract and no llms.txt; the only key travels as a query parameter\n\n\n## Why the edge\n\n### Schema \u0026 documentation: Ride with GPS API +30\n\n- Ride with GPS API (72): Public OpenAPI 3.0.1 file with 34 paths, 61 operations and 41 schemas (25). ridewithgps.com/llms.txt describes the product and plans but links no Markdown docs, and the documentation is HTML (5 of 10). Operation descriptions say which endpoints are organisation-only, that uploads and package builds return a task to poll, how experience codes replace each other and that deleting a member keeps their account; little on when not to use an operation (14 of 20). 18 enums, required fields and defaults in the file, but the Error schema is an array of strings (10 of 15). One example in the OpenAPI file, request and pagination examples on the docs pages, and a table of HTTP codes with the `errors` array shape (8 of 15). One version in the path, a rule that only incompatible changes create a new version, and a dated change log back to January 2025 (15). 25 + 5 + 14 + 10 + 8 + 15 = 72.\n- Ticketmaster Discovery API (42): No OpenAPI or other machine-readable contract found; the API Explorer is interactive only (0 of 25). No llms.txt or Markdown docs (0). Each endpoint is documented with its purpose, parameters and defaults, but nothing says when not to use one (12 of 20). Typed parameters with enums (includeTest yes, no, only; includeSpellcheck; sort keys; source) and defaults, with required fields limited to the key (12 of 15). Sample requests and full JSON responses for each endpoint, but the only documented error is the 401 for a bad key, with no error catalogue for Discovery (10 of 15). v2 in the path, Partner and Inventory Status release notes with dates, but no changelog for the Discovery API on the live portal (8 of 15). Total 42.\n\n### Reliability: Ticketmaster Discovery API +21\n\n- Ride with GPS API (24): Read with the hosted lines. No status page, since status.ridewithgps.com answers 301 to the home page and the docs link none (0). No readable incident history (5). The API terms of 11 September 2026 say no fixed request limits currently apply and ask for caching, webhooks and backing off, so there are no numbers to publish (5 of 15). No 429 is documented in the docs or the OpenAPI file; the terms ask clients to back off on failures, uploads run as tasks to poll, and no idempotency key exists for the 30 write operations (4 of 15). No SLA (0). v1 is the current and only version with no beta label (10). 0 + 5 + 5 + 4 + 0 + 10 = 24.\n- Ticketmaster Discovery API (45): Read with the hosted lines. The portal has an API status page at /support/api-status/, but it renders by script and showed no components or history to our reader, so the line is part met (5 of 20). No readable incident history (5). Default limits stated in numbers, 5,000 calls a day and 5 a second on the getting started page, 2 a second in the FAQ (15). 429 over quota with Rate-Limit-Over and Rate-Limit-Reset headers, no Retry-After or backoff guidance, and the graded surface only reads (10 of 15). No SLA found (0). Discovery v2 has been general since January 2016 (10). Total 45.\n\n### Security \u0026 auth: Ride with GPS API +12\n\n- Ride with GPS API (30): OAuth 2.0 authorisation code flow with one scope, `user`, and a revoke endpoint, but no PKCE, expiry or refresh token is documented; basic auth tokens are minted from the account email and password with no documented expiry or revocation; credentials travel in headers (18 of 30). No read-only scope, and the 30 write operations, including deletes of routes, events, members and experiences, need no confirmation (4 of 20). Route names, descriptions, event text and experience messages are user content with no guidance on treating them as untrusted (5 of 15). The API clients page lists clients and tokens; no call log is documented (3 of 15). /.well-known/security.txt returns 404, and no disclosure policy, bug bounty or certification was found (0 of 20). 18 + 4 + 5 + 3 + 0 = 30.\n- Ticketmaster Discovery API (18): One key per app with no scopes, sent as the apikey query parameter as the documented route, so 10 less 10 (0 of 30). The open key reaches only the read-only Discovery surface; reserve and purchase need partner approval (10 of 20). Event and attraction descriptions are promoter-written content, with no injection guidance (5 of 15). Rate-limit headers give per-call usage, no audit log (3 of 15). No security.txt (404 on both hosts), no disclosure policy, bug bounty or certification found on the portal (0 of 20). Total 18.\n\n### Maintenance \u0026 community: Ride with GPS API +12\n\n- Ride with GPS API (60): Read for a closed service. The newest change log entry is 14 October 2026 (30). Five dated entries since 4 August 2026, on 10 August, 3 September, 11 September, 6 October and 14 October (20). A dated change log, developers@ridewithgps.com and a Zendesk help centre that answered 403 to our reader; replies were not tested (10 of 15). No official SDK and no entry in the official MCP registry (0 of 15). No package or CI to judge (0 of 10). 30 + 20 + 10 + 0 + 0 = 60.\n- Ticketmaster Discovery API (48): Read for a closed service. The newest dated API change on the portal is the Partner API release note of 16 October 2026; none was found for the Discovery API itself, so the line is part met (20 of 30). Partner API notes dated 4, 11, 19 and 31 August and 16 October 2026 make three in 90 days (20). A developer support form with replies by email, a 48-hour promise for affiliate questions, and no public forum (8 of 15). The GitHub SDKs were last pushed between 2016 and 2021, the Java one is archived, and there is no entry in the MCP registry (0 of 15). The SDK repositories are stale (0 of 10). Total 48.\n\n### Agent ergonomics: Ticketmaster Discovery API +6\n\n- Ride with GPS API (57): No field selection; polylines and track files sit on separate endpoints and page_size runs from 20 to 200 (12 of 25). page and page_size with meta.pagination, filters for name, visibility, distance, elevation gain, archived and stationary, and privacy_code for non-public items (20). Errors carry HTTP codes and an `errors` array of messages with no codes to branch on (10 of 20). Reads are safe to repeat and package builds return 409 while one runs, but no idempotency key covers creates, and deletes are not confirmed (8 of 20). Two headers and a .json suffix are all a request needs, with no official SDK (7 of 15). 12 + 20 + 10 + 8 + 7 = 57.\n- Ticketmaster Discovery API (63): Pages of up to 200 events by size, but no field selection, and each event carries nested dates, sales, classifications, images, price ranges, promoter, venue and links (12 of 25). Paging by size and page with the 1,000-item depth limit, keyword, date, location, radius, classification, source and locale filters, and sort keys (18 of 20). 401 carries a faultstring and errorcode, 429 has headers, but no other error body is documented for Discovery (10 of 20). The surface is read-only and safe to retry (15 of 20). One required parameter, sensible defaults, but no current official SDK; the GitHub SDKs date from 2016 to 2021 (8 of 15). Total 63.\n\n### Transparency \u0026 trust: Ticketmaster Discovery API +6\n\n- Ride with GPS API (59): 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 App Store names Ride with GPS LLC (15 of 30). The privacy policy of 31 July 2026 gives no fixed retention periods, names Google Maps, Google and Apple and other providers only by category, and names no entity (12 of 30). The API terms promise reasonable advance notice of material changes through the change log or email, and the 23 March 2026 breaking change to activity_types shipped with a migration map and no notice window (10 of 20). Processing in the United States and other jurisdictions with safeguards where required; no subprocessor list (6 of 20). 15 + 12 + 10 + 6 = 43.\n- Ticketmaster Discovery API (65): Closed service with clear terms naming Live Nation Entertainment, Inc. under California law, last updated 27 June 2023 (15 of 30). The privacy policy of 29 July 2026 names the controller, retention (deletion within 90 days of a request, 7 years of inactivity, longer for tax records) and providers, and agrees with itself; no DPA for developers (22 of 30). Deprecations are announced (the XML feed, the International Discovery API folding into Discovery, null price fields) without notice periods (8 of 20). Providers named (Braintree, Zendesk, Concentrix, Salesforce, Ekata, OneTrust, Forter) with the platform run from the United States and United Kingdom and Standard Contractual Clauses for transfers (14 of 20). Total 59.\n\n## Score by category\n\n| Category | Weight | Ride with GPS API | Ticketmaster Discovery API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 24 | 45 | Ticketmaster Discovery API +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 72 | 42 | Ride with GPS API +30 |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 63 | Ticketmaster Discovery API +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 30 | 18 | Ride with GPS API +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 30 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 60 | 48 | Ride with GPS API +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 59 | 65 | Ticketmaster Discovery API +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **45.2 · E** | **42.9 · E** | |\n\n## Facts side by side\n\n| Fact | Ride with GPS API | Ticketmaster Discovery API |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Ride with GPS, Inc. | Ticketmaster (Live Nation Entertainment) |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | HTTP | |\n| Auth | OAuth or key | API key |\n| Pricing | Freemium | Free |\n| x402 | no | no |\n| Licence | Proprietary service under the Ride with GPS API Terms of Service (effective 11 September 2026) | Proprietary service. Developer portal General Terms of Use last updated 27 June 2023; privacy policy last updated 29 July 2026 |\n| Tools exposed | 0 | none |\n| Read-only variant documented | yes | no |\n| llms.txt | yes | no |\n| Last release | 2026-10-14 | 2026-10-16 |\n| Terms last updated | 2026-09-11 | 2023-06-27 |\n| Privacy policy last updated | 2026-07-31 | 2026-07-29 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | yes |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n\n## Verdicts\n\n**Ride with GPS API.** 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.\n\n**Ticketmaster Discovery API.** The Discovery API gives a free key 5,000 event searches a day across Ticketmaster's markets, with documented paging, filters and rate-limit headers. There is no OpenAPI contract or current SDK, the key travels in the URL, the terms forbid revenue from the API, and purchase stays behind the partner-only Partner API.\n\n## Before you call either\n\n### Ride with GPS API\n\n1. 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\n2. Append .json to endpoints or set `content-type: application/json`, and read the root key named after the resource (`route`, `trip`)\n3. 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\n4. 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\n5. 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\n\n### Ticketmaster Discovery API\n\n1. Search with `GET https://app.ticketmaster.com/discovery/v2/events.json?apikey=...\u0026keyword=...\u0026countryCode=...` and page with size and page while size times page stays under 1,000\n2. Keep under 5 calls a second and 5,000 a day per key; read Rate-Limit-Available and Rate-Limit-Reset and stop on 429\n3. Do not try to buy tickets through the API; hand the person the event's url field, and expect the Partner API to refuse keys that are not partner-approved\n4. Pull whole-country data from the Discovery Feed rather than paging the API, and keep caches short since the terms allow only reasonable periods\n5. Treat event and attraction descriptions as promoter-written content, and never put the apikey in logs or shared URLs\n\n## Questions\n\n### Which is better for AI agents, Ride with GPS API or Ticketmaster Discovery API?\n\nRide with GPS API scores 45.2 (E) on agent readiness against Ticketmaster Discovery API's 42.9 (E), and leads in 3 of 7 scored categories. Ticketmaster Discovery API leads on reliability, agent ergonomics and transparency \u0026 trust.\n\n### Do Ride with GPS API and Ticketmaster Discovery API need an API key?\n\nRide with GPS API takes an API key or an OAuth sign-in. Ticketmaster Discovery API needs an API key.\n\n### Can an agent call Ride with GPS API and Ticketmaster Discovery API without installing anything?\n\nNo hosted endpoint is listed for Ride with GPS API. No hosted endpoint is listed for Ticketmaster Discovery API.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster.json, and with the fewest tokens: https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"ride-with-gps\", \"b\": \"ticketmaster\"}`. From a terminal: `anchor compare ride-with-gps ticketmaster`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/ride-with-gps.json and https://www.anchorterminal.com/api/v1/tools/ticketmaster.json\n\n## Other comparisons with Ride with GPS API or Ticketmaster Discovery API\n\n- [Ride with GPS API vs Strava MCP Connector + API](https://www.anchorterminal.com/compare/ride-with-gps-vs-strava.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-04", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Ride with GPS API vs Ticketmaster Discovery API", "url": "" } ], "description": "Ride with GPS scores 45.2 (E) to Ticketmaster Discovery's 42.9 (E) for hobbies events. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Ride with GPS API E 45.2", "Ticketmaster Discovery API E 42.9", "scores" ], "h1": "Ride with GPS API vs Ticketmaster Discovery API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/ride-with-gps-vs-ticketmaster", "published": "2026-10-01", "section": "tools", "title": "Ride with GPS vs Ticketmaster Discovery for AI agents (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/ride-with-gps-vs-ticketmaster" }, "tokens": { "markdown": 4250, "slim": 2830 }, "version": 1 }