Ride with GPS API
by Ride with GPS, Inc. HTTP API in Hobbies, sport & recreation
Ride with GPS, Inc. · ridewithgps.com since 2007 · who's behind it
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.
Best for An agent planning or reading cycling routes and rides for a consenting person, or running a club's calendar from an organisation account.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Hobbies. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
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
Access how an agent reaches and pays for it
- Transport
- HTTP
- Auth
- OAuth or key
- Pricing
- Freemium · $9.99 / mo
- x402
- No
- Licence
- Proprietary service under the Ride with GPS API Terms of Service (effective 11 September 2026)
- Tools exposed
- 0
- Capabilities
- hobbies.routes hobbies.activities hobbies.events
Where it lives packages, source, docs and releases
- llms.txt
- published
- Last release
From our research 9 facts checked against the vendor's pages
- 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
userand 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
errorsarray 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
Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
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
userscope 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
Before you call it notes for agents
- 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
Who's behind it provenance 74/100
- Legal entity namedRide with GPS, Inc.20/20
- Domain ageridewithgps.com, registered 2007-04-16 (19 years)15/15
- Endpoint on the vendor's domainridewithgps.com15/15
- Terms of serviceread, states 2 of the 7 things a reader expects, and has 1 clause that costs points3.7/10
- Privacy policyread, states 7 of the 8 things a reader expects9.3/10
- Status pagenot found0/10
- Changelogpublished10/10
- security.txtnot found0/10
- People named4 named with their role, none with a public profile7/10
- Support routea support address, help pages5/5
Terms and privacy, as read
Terms of service dated 2026-09-11, states 2 of 7, 2 to know
TL;DR Dated 2026-09-11. States 2 of the 7 things a reader expects, and we didn't find the governing law, a liability limit, how changes are announced, what users may not do or 1 more. To know before relying on it, changes without notice and cut-off without notice or for any reason.
Says the terms or the service can change without noticecosts points
We may make changes without advance notice when needed for security, privacy, legal compliance, abuse prevention, or the health of the service.
A customer may not hear about a change before it applies.
Says access can be ended without notice or for any reason
We may act without advance notice when prompt action is needed to protect users, Ride with GPS, or others.
The vendor can suspend or close an account without warning, which would stop an agent mid-task.
Gives the date it was last updated Last updated 2026-09-11
Effective September 11, 2026
Without a date nobody can tell which version they agreed to.
Names the governing law or courts
Not found in the text.
Says where a dispute would be heard and under whose law.
States a limit on its liability
Not found in the text.
Says the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
We may throttle, reject, or block traffic, suspend credentials, or end API access if we reasonably believe use is abusive, harmful, unlawful, deceptive, insecure, or likely to disrupt the API or Ride with GPS.
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced
Not found in the text.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
Not found in the text.
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment
Not found in the text.
Says whether availability is promised and where the promise is written.
The document is the API terms, which supplement the main Terms of Service where the warranty disclaimers and liability limits sit.
The API is provided under the warranty disclaimers and limitations of liability in the Ride with GPS Terms of Service.
Noted by a second reader on 2026-11-03.
Commercial use of the API needs no paid plan, commercial agreement or prior approval.
You do not need a paid Ride with GPS plan, a commercial agreement, or prior approval.
Noted by a second reader on 2026-11-03.
There are no fixed request rate limits at present, and the vendor may introduce them later.
We do not currently impose fixed request rate limits.
Noted by a second reader on 2026-11-03.
The document · read 2026-11-03 · 928 words
Privacy policy dated 2026-07-31, states 7 of 8
TL;DR Dated 2026-07-31. States 7 of the 8 things a reader expects, and we didn't find where data goes. The rules found no clause to flag.
Gives the date it was last updated Last updated 2026-07-31
This privacy policy was last updated on July 31, 2026.
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
When you create a Ride with GPS account or log in using a third-party service such as Google or Apple, we may collect your name, email address, and a unique identifier provided by the service.
The basic statement a privacy policy exists to make.
Says how long data is kept For as long as needed, with no period named
We retain your personal data, including account details and usage information, as long as it is necessary to facilitate your use of Ride with GPS.
Says when data sent to the service is deleted.
Says who else receives the data
We may share personal information with trusted third-party service providers who perform services on our behalf, such as hosting, analytics, advertising and marketing measurement, payment processing, communications delivery, customer support, security, fraud prevention, and mapping or geospatial services (including pr…
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising Says it does not sell personal data
Ride with GPS does not sell personal information as defined under California law.
A plain statement either way.
Says what rights people have over their data
You have the right to delete your account and related personal information at any time.
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact
If you have any questions or concerns regarding this privacy policy, or you wish to contact us, our contact information is as follows:
An address or officer to send a request to.
Says where data is transferred or stored
Not found in the text.
The countries data goes to and the safeguard used.
Content and accounts may be restricted or removed by automated systems with limited human involvement, occasionally in error.
These systems may operate with limited human involvement and may occasionally remove content in error.
Noted by a second reader on 2026-11-03.
The document · read 2026-11-03 · 1,649 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
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.
Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Zack HamFounder and CEO
- Cullen KingFounder and CTO
- Kevin PrenticeDirector of Business Operations
- Helene RidellaDirector of Operations
Ride with GPS, Inc. on @ridewithgps
Researched 3 November 2026 from public pages. The about page, read 3 November 2026, names Zack Ham (Founder & CEO), Cullen King (Founder & CTO), Kevin Prentice (Director of Business Operations) and Helene Ridella (Director of Operations), gives 2007 as the founding year and says the company remains founder-owned. llms.txt adds Portland, Oregon. No personal LinkedIn, X or GitHub account is linked from a first-hand page, so none is recorded. Investors were looked for on the about page, llms.txt, the terms and privacy policy and the news page link; the about page says everything the company makes goes back into the platform and names no investor, so none is listed. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-04 15:54 UTC
- security.txt none · 3 hours ago
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/ride-with-gps.json
Notable
- Public OpenAPI 3.0.1 file with 34 paths and 61 operations, 30 of them writes, on 3 November 2026; no 429 and one example in the file source
- The API Terms of Service, effective 11 September 2026, say anyone may use the API with an account and a client, commercial use is allowed, no attribution is required, and no fixed request limits apply today, with webhooks preferred to polling source
- The dated API change log records experiences endpoints on 14 October 2026, route and trip updates on 6 October, GPX, TCX, FIT and KML downloads on 3 September, uploads and tasks on 30 July, and a breaking change to route activity_types on 23 March 2026 with a migration map and no notice window source
- Webhooks for route and trip create, update, delete, pin and unpin, signed with HMAC-SHA256 in x-rwgps-signature, up to 100 notifications a request, no retries and a 1-second response window source
- Club member, experience and point-of-interest endpoints are restricted to organisation accounts, which are priced by email source
- No status page, since status.ridewithgps.com redirects to the home page. No security.txt (404). No entry in the official MCP registry source
- The terms of service of 1 July 2026 name Ride with GPS, Inc, a Delaware corporation, under Oregon law; the App Store seller is Ride with GPS LLC source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Ride with GPS API, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Ride with GPS API, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 3 November 2026 | 16%20 | 4.8 | |
| 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. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 3 November 2026 | 13%16.2 | 11.7 | |
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. | |||
| Agent ergonomicschecked 3 November 2026 | 13%16.2 | 9.3 | |
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. | |||
| Security & authchecked 3 November 2026 | 14%17.5 | 5.2 | |
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. | |||
| Payments & pricingchecked 3 November 2026 | 10%12.5 | 3.8 | |
| Read with the hosted rubric. No x402, MPP or L402 (0). The API is free under the terms and the plan prices are stated in llms.txt and the App Store listing, but the pricing page shows no figures to our reader and organisation accounts, which the member, event, experience and point-of-interest endpoints need, are priced by email (10 of 20). A free Starter account and a free API client with no card (20). A person signs up and creates the API client in a browser, and basic auth tokens need the account password (0). 0 + 10 + 20 + 0 = 30. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 3 November 2026 | 7%8.8 | 5.2 | |
| 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. | |||
| Transparency & trusteditorial 43, provenance 74checked 3 November 2026 | 7%8.8 | 5.2 | |
| 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. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 45.2 · E | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 45.2 E methodology v0.7
Fix list 18 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Ride with GPS API. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: support.ridewithgps.com, which answered 403, and changelog.ridewithgps.com, whose entries did not render; responsiveness rests on the API change log and the developer address.
- unchecked: OAuth token lifetime, refresh and PKCE, and basic auth token expiry and revocation, which the guide does not state and which need a client to observe.
- The pricing page renders plan tiers without figures to our reader; the figures come from llms.txt and the App Store listing and agree with each other.
- The terms name Ride with GPS, Inc (Delaware) and the App Store names Ride with GPS LLC; the privacy policy names neither. The listing uses the terms' name.
- firstReleased is 8 January 2025, the earliest change log entry. The API existed before that date; an earlier first-hand date was not found.
- The 6 October 2026 rename of friends_only to mutual_followers_only is not labelled breaking and the entry does not say whether the old value still works.
Sources 18
- API documentation ridewithgps.com · seen 2026-11-03
- OpenAPI 3.0.1 file ridewithgps.com · seen 2026-11-03
- authentication guide ridewithgps.com · seen 2026-11-03
- webhooks guide ridewithgps.com · seen 2026-11-03
- API Terms of Service (11 September 2026) ridewithgps.com · seen 2026-11-03
- API change log ridewithgps.com · seen 2026-11-03
- llms.txt ridewithgps.com · seen 2026-11-03
- terms of service (1 July 2026) ridewithgps.com · seen 2026-11-03
- privacy policy (31 July 2026) ridewithgps.com · seen 2026-11-03
- pricing page ridewithgps.com · seen 2026-11-03
- organisation accounts ridewithgps.com · seen 2026-11-03
- about page ridewithgps.com · seen 2026-11-03
- App Store listing (prices, seller) apps.apple.com · seen 2026-11-03
- status.ridewithgps.com (301 to home) status.ridewithgps.com · seen 2026-11-03
- security.txt (404) ridewithgps.com · seen 2026-11-03
- robots.txt ridewithgps.com · seen 2026-11-03
- MCP registry search (empty) registry.modelcontextprotocol.io · seen 2026-11-03
- RDAP for ridewithgps.com rdap.verisign.com · seen 2026-11-03
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Freemium $9.99 / mo 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.
Prices
| Item | Price | Unit | Note |
|---|---|---|---|
| Basic plan | $9.99 | per month (plan) | $59.99 a year; the API itself is free |
| Premium plan | $12.99 | per month (plan) | $79.99 a year, 7-day trial |
Compared across listings on the price index.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/ride-with-gps.xml, or this listing's score history at history.json.
Connect
First request
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"Through letme picks today, calling later
GET https://letme.dev/ride-with-gpsletme picks this listing for hobbies.events, because it's the top-graded tool for the job.
letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Ride with GPS API
#2 of 6 in Best hobby, sport and recreation APIs for AI agents · All 3 hobbies comparisons
Strava MCP Connector + API ETicketmaster Discovery API E
Head to head Ride with GPS API vs Ticketmaster Discovery API · Ride with GPS API vs Strava MCP Connector + API
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Strava MCP Connector + API Strava, Inc. | E | 45.8 | hobbies.activities hobbies.routes | no |
| Ticketmaster Discovery API Ticketmaster (Live Nation Entertainment) | E | 42.9 | hobbies.events | no |
| Chess.com Published-Data API Chess.com LLC | E | 40.8 | same category | no |
| Rebrickable Rebrickable | F | 34.7 | same category | no |
| Ravelry Ravelry, LLC | F | 16.5 | same category | no |
Machine-readable
- JSON
/api/v1/tools/ride-with-gps.json· historyhistory.json· badge/badges/ride-with-gps.svg· changes feed/feeds/tools/ride-with-gps.xml - Markdown
/tools/ride-with-gps.md· slim/tools/ride-with-gps.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/ride-with-gps.md·/fixes/ride-with-gps.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool ride-with-gps --md(the CLI) · over MCPget_tool {"slug": "ride-with-gps"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT ride-with-gps.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/ride-with-gps"><img src="https://www.anchorterminal.com/badges/ride-with-gps.svg" alt="Ride with GPS API on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/ride-with-gps)<a href="https://www.anchorterminal.com/tools/ride-with-gps">Ride with GPS API on Anchor Terminal</a>It counts on a page on ridewithgps.com or one of its subdomains.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "ride-with-gps", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Ride with GPS API is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/ride-with-gps. The logo is the one on this listing. If it's wrong or out of date, send us the right one.