# MapTiler Cloud > MapTiler Cloud is a hosted maps platform from MapTiler AG in Switzerland. Its read-only REST APIs serve map styles, vector and raster tiles, static maps, forward and reverse geocoding, IP geolocation, elevation, coordinate transforms and weather data. - Canonical: https://www.anchorterminal.com/tools/maptiler - Pricing: https://www.anchorterminal.com/tools/maptiler#pricing - Reviews: https://www.anchorterminal.com/tools/maptiler#reviews - Markdown: https://www.anchorterminal.com/tools/maptiler.md (~6,700 tokens) - Slim: https://www.anchorterminal.com/tools/maptiler.min.md (~1,630 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/maptiler.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT maptiler.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-07 ## Overview **Grade B · 62.1/100 · rank #574 of 1486 · #10 in Maps, geocoding & places · not agent-ready · confidence medium** ## Assessment MapTiler Cloud has an OpenAPI 3.1 reference, llms.txt with Markdown pages, an agent skill and ISO 27001 certification, and allows geocoding results to be stored. The key always travels in the query string, there's no routing API, no documented rate limit or 429 handling, and the free plan excludes commercial use. ## Facts | Field | Value | | --- | --- | | Vendor | MapTiler AG (https://www.maptiler.com) | | Kind | HTTP API | | Category | Maps, geocoding & places (https://www.anchorterminal.com/categories/maps) | | Transport | HTTP | | Auth | API key · API key from the MapTiler Cloud account after a browser signup, always passed as the `key` query parameter. Keys can be limited to HTTP origins and a User-Agent substring and are managed through the Service API. From a backend, a service token can sign each request with a `signature` parameter instead. The Service API (uploads, tilesets, keys, analytics) needs a service token. | | Pricing | Freemium ($0.15 / 1k req) · Free plan with 100,000 API requests, 5,000 sessions and 1,000 search sessions a month, no card, for testing and non-commercial use; service pauses at the limit. Flex is $30 a month with 500,000 requests, then $0.15 per 1,000 requests and $2.50 per 1,000 search sessions. Custom contracts carry a 99.9% SLA. | | x402 | No · No x402, MPP or L402 in the API reference, OpenAPI spec, llms.txt or pricing page (checked 2026-11-06). Paid plans are billed by FastSpring. | | Licence | unknown | | Packages | npm: `@maptiler/client`; npm: `@maptiler/sdk` | | Source | https://github.com/maptiler/maptiler-client-js | | Docs | https://docs.maptiler.com/cloud/api/ | | llms.txt | https://docs.maptiler.com/llms.txt | | Last release | 2026-10-02 | | npm downloads / week | 114,682 | | Surface listed | The public REST APIs at api.maptiler.com, read from docs.maptiler.com (API reference, OpenAPI spec, llms.txt, guides and updates), the pricing, terms, Cloud terms, privacy and security pages, status.maptiler.com and the maptiler GitHub repositories on 6 November 2026. No account was made and no key was used | | Public APIs | Maps, Static maps, Tiles, Data (your datasets as GeoJSON), Images, Geocoding (forward, reverse, by ID and batch of up to 50 queries), Geolocation by IP, Coordinates, Elevation, Weather and fonts and sprites. All read-only | | Service API | Upload, Tileset, API keys and Analytics APIs for managing the account, with a service token | | No routing | No directions or route matrix endpoint in the API reference | | Plans | Free (100,000 requests, 5,000 sessions, 1,000 search sessions a month, non-commercial), Flex $30 a month (500,000 requests, 25,000 sessions, 3,000 search sessions), Custom with soft limits and a 99.9% SLA | | Rate limits | Monthly quotas per plan. No per-second limit or 429 behaviour found in the reviewed documentation. A spending limit on Flex and Custom stops the API when reached | | Storage terms | Map content can't be cached server-side. Geocoding results may be bulk downloaded and used outside the service with attribution | | Hosting | Customer data stored and processed mainly in Switzerland and the EEA on OVHcloud and Google Firebase, with an EU-only endpoint at api.maptiler.eu | | SDKs | @maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 (both 2 October 2026, BSD 3-Clause), plus native mobile SDKs. No official Python client found | | Legal entity | MapTiler AG, Unterägeri, Switzerland, under Swiss law with courts in Zug | | Capabilities | geo.geocode, geo.reverse, geo.places, geo.tiles, data.weather | | Tags | hosted, api-key, freemium, free-tier, no-card, llms-txt, openapi, official, agent-skills, typescript, status-page, security-txt, iso27001, eu, eu-region, sla, closed-source | | JSON | https://www.anchorterminal.com/api/v1/tools/maptiler.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-06 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 43 | 8.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 79 | 12.8 | | Agent ergonomics | 13% | 16.2 | 70 | 11.4 | | Security & auth | 14% | 17.5 | 64 | 11.2 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 70 | 6.1 | | Transparency & trust (editorial 64, provenance 96) | 7% | 8.8 | 80 | 7.0 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **62.1 → B** | ### Why each score - Reliability 43 (checked 2026-11-06): Hosted lines. status.maptiler.com is a StatusCake public uptime report rather than a component incident page (15). Its data loads from app.statuscake.com, whose robots.txt answered with a redirect, so we didn't fetch it and read no history. That's our limit, not a finding, and the rubric gives 5 (5). Monthly request and session quotas are published per plan, but no per-second limit (5). No 429, Retry-After or backoff guidance found in the API reference, the OpenAPI spec or llms-full.txt (0). The pricing page lists a 99.9% SLA on the Custom plan, while the Cloud terms call availability best effort and point to a custom SLA (8). The public APIs are GA (10). 15+5+5+0+8+10 = 43. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 79 (checked 2026-11-06): OpenAPI 3.1.0 document with 32 paths for the public APIs (25). llms.txt, llms-full.txt and a Markdown twin of every page (10). Each API page says what it's for and when to use the SDK instead (session billing), with little on when not to call it (13). Parameters are typed with defaults, such as limit (default 5 forward, 1 reverse) and a types enum, but bbox and proximity are strings (11). Examples on every endpoint, and the spec documents 400, 403, 404 and 414, without an error reference page (10). A dated platform updates page and a geocoding index changelog, but no version in the API path and the spec is version '1.0' (10). 25+10+13+11+10+10 = 79. - Agent ergonomics 70 (checked 2026-11-06): API reading. limit, types, bbox, proximity, country, language and fuzzyMatch size geocoding results, and the batch endpoint takes up to 50 queries (20). Country, bbox and type filters, no pagination (geocoding rarely needs it) (16). Errors are documented as 400 and 403 with no recovery guidance (10). Every public API reads and is safe to retry (12). Few required parameters, but official clients are JavaScript and TypeScript only, plus native mobile SDKs (12). 20+16+10+12+12 = 70. - Security & auth 64 (checked 2026-11-06): Revocable keys that can be limited to origins and a User-Agent substring and managed by the API keys API, and service tokens that sign requests so the token itself never travels, which earns 27. Less 10 because the key is 'always passed as a query parameter' (17). The public APIs are read-only, and account changes need a separate service token (16). Geocoding returns OpenStreetMap names and addresses, community-edited text, with no prompt-injection guidance (7). An Analytics API and account usage statistics (8). security.txt, a vulnerability disclosure policy and ISO/IEC 27001:2022 certification per the security page. No bug bounty found (16). 17+16+7+8+16 = 64. - Payments & pricing 40 (checked 2026-11-06): No x402, MPP or L402 (0). Per-1,000 prices for requests ($0.15) and sessions ($2.50) public without login (20). Free plan with no card, though only for testing and non-commercial use (20). Signup is a browser flow (0). 0+20+20+0 = 40. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 70 (checked 2026-11-06): @maptiler/client 3.1.0 and @maptiler/sdk 4.2.0 on 2 October 2026, 35 days before this check, with the agent skill updated on 21 October (20). Platform updates entries for August (EU endpoint, key security) and September 2026 (terrain blending) plus the two October releases (20). A Discord community and support answered on a best-effort basis within two business days, per the Cloud terms. We didn't read GitHub issues (10). Official JavaScript client and SDK current, no Python client (12). The SDK repository runs unit and end-to-end tests in CI; we didn't check results (8). 20+20+10+12+8 = 70. - Transparency & trust 80 (checked 2026-11-06): Editorial half only. Closed service with general and Cloud-specific terms under Swiss law, and SDKs under BSD 3-Clause and the skill under MIT (20). The privacy policy covers account and payment data and says legal-claim data is kept up to 10 years, but says nothing about how long API request logs are kept (15). A dated deprecation page for v3 maps and migration guides, with no written notice period (12). Hosting with OVHcloud and Google Firebase, data mainly in Switzerland and the EEA, and an EU-only endpoint. Google Analytics, Firebase and FastSpring named in the privacy policy (17). 20+15+12+17 = 64. Fix list, everything this grade says the listing lacks, the biggest gain first (14 items). What it covers is at https://www.anchorterminal.com/fixes/maptiler.md (JSON https://www.anchorterminal.com/fixes/maptiler.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "maptiler", "plan": "read"}`, free while the beta runs ### What we couldn't check - unchecked: uptime and incident history on status.maptiler.com, whose data host app.statuscake.com answered robots.txt with a redirect - unchecked: GitHub stars and issue reply times, because the GitHub API was rate-limited for us on 6 November 2026 - firstReleased is left unset, since no first-hand launch date for MapTiler Cloud was found on the pages read - The privacy policy doesn't say how long API request logs or IP addresses are kept ### Sources - API overview: (seen 2026-11-06) - OpenAPI spec: (seen 2026-11-06) - llms.txt: (seen 2026-11-06) - geocoding API reference: (seen 2026-11-06) - authentication guide: (seen 2026-11-06) - platform updates: (seen 2026-11-06) - pricing: (seen 2026-11-06) - general terms: (seen 2026-11-06) - Cloud terms: (seen 2026-11-06) - privacy policy: (seen 2026-11-06) - security page: (seen 2026-11-06) - security.txt: (seen 2026-11-06) - agent skill: (seen 2026-11-06) - JavaScript client tags: (seen 2026-11-06) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/maptiler/history.json - 2026-11-06: graded 62.1 B (methodology 0.7) ## Who's behind it (provenance 96/100, checked 2026-11-06) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | MapTiler AG | 20/20 | | Domain age | maptiler.com, registered 2008-08-08 (18 years) | 15/15 | | Endpoint on the vendor's domain | maptiler.com | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects | 8.3/10 | | Privacy policy | read, states 4 of the 8 things a reader expects | 7/10 | | Status page | status.maptiler.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | | People named | 1 named with their role, none with a public profile | 7/10 | | Support route | help pages, a community | 5/5 | The general terms name MapTiler AG, Zugerstrasse 22, 6314 Unterägeri, Switzerland, under Swiss law with courts in Zug. security.txt at www.maptiler.com/.well-known/security.txt names sysadmin@maptiler.com, a PGP key and a signature, and has no Expires field. status.maptiler.com is a StatusCake public report whose data loads from app.statuscake.com. That host's robots.txt answered with a redirect, so it wasn't fetched and no uptime or incident history was read. RDAP gives maptiler.com a registration date of 8 August 2008. No clause on automated access to the website was found in the general terms. robots.txt on www.maptiler.com and docs.maptiler.com allows all agents apart from a few paths. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.maptiler.com/terms/), read 2026-11-06, gives no date, states 5 of the 7 things a reader expects. - To know. Requires arbitration or waives class actions. "The Parties commit to using arbitration only as a last resort, and to make the best effort to resolve all disputes directly between the two parties, including escalation to manager level if required." - Not found in the text. Gives the date it was last updated. - Names the governing law or courts. Disputes go to the courts of Zug. - States a limit on its liability. Capped at the fees paid in the 3 months before the claim or USD 1000. - Not found in the text. Says how changes to the terms are announced. **Privacy policy** (https://www.maptiler.com/privacy-policy/), read 2026-11-06, gives no date, states 4 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Says how long data is kept. Names a period of 10 years. - Not found in the text. Says who else receives the data. - Not found in the text. Gives a privacy contact. - Not found in the text. Says where data is transferred or stored. ## Humans behind the project (researched 2026-11-06 from public pages, not part of the grade) ### Key people - Petr Pridal, CEO - Note: MapTiler's company page, read on 6 November 2026, names Petr Pridal as CEO and says he began assembling the MapTiler team after a decade of freelance, research and open-source work, and OVHcloud's startup profile says MapTiler was founded by a team of geospatial engineers and entrepreneurs led by Petr Pridal, so he is marked as founder. No other people are named there, and no personal accounts are linked. Headquarters are in Zug, Switzerland, with part of the development team in Brno, Czechia. Startupticker's report on MapTiler AG says the company is bootstrapped with multi-million revenue, and CzechCrunch (10 January 2020) says the project runs entirely without investors, is long profitable and that both companies behind it, OctoGEO and Klokan Technologies, are owned by Petr Přidal. No investor is named on the company, terms or security pages or in a web search on 6 November 2026, so investors, total raised and valuation are left out; competition prizes and grants such as ESA BIC aren't investments. - MapTiler: LinkedIn https://www.linkedin.com/company/maptiler X https://x.com/MapTiler GitHub https://github.com/maptiler ### Getting support - Discord: https://discord.com/invite/4NGjwUFGj4 - Help: https://docs.maptiler.com/support/requests/ - Help: https://www.maptiler.com/#contact - General contact: sysadmin@maptiler.com - Sources: https://www.maptiler.com/company/, https://www.maptiler.com/terms/, https://www.maptiler.com/.well-known/security.txt, https://www.maptiler.com/terms/cloud/, https://blog.ovhcloud.com/startup-success-highlight-maptiler/, https://www.startupticker.ch/en/news/maptiler-s-international-growth-results-in-a-swiss-launch, https://cc.cz/cesi-vyviji-konkurenci-google-map-kterou-kazdy-mesic-vyuzije-200-milionu-lidi-jejich-mapy-nasadila-i-nasa/ ## Live (updated 2026-11-07 15:59 UTC) - Vendor status page: not read, no machine-readable status found - github `maptiler/maptiler-client-js` v3.1.0, released 2026-10-02 - npm `@maptiler/client` 3.1.0 - npm `@maptiler/sdk` 4.2.1 - security.txt: valid - Watching changelog - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/maptiler.json ## 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. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | API requests over the Flex allowance | $0.15 | per 1,000 requests | Flex includes 500,000 a month | | Search sessions over the Flex allowance | $2.50 | per 1,000 requests | Priced per 1,000 search sessions through MapTiler SDK JS | | Flex plan | $30 | per month (plan) | Extra usage billed monthly | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - OpenAPI 3.1.0 spec, llms.txt, llms-full.txt and a Markdown version of every docs page - Geocoding results may be bulk downloaded and used outside the service with attribution - Keys can be restricted by origin and User-Agent, and service tokens can sign requests instead - ISO/IEC 27001:2022 certification, security.txt and a vulnerability disclosure policy - EU-only endpoint at api.maptiler.eu and hosting mainly in Switzerland and the EEA ## Weaknesses - The API key is always sent as a query parameter - No routing, directions or matrix API - No per-second rate limit, 429 behaviour or retry guidance found in the documentation - The free plan is for testing and non-commercial use only, and pauses at its monthly limit - Official clients are JavaScript and TypeScript only ## Before you call it (notes for agents) 1. Restrict the key to an origin or User-Agent, or sign requests with a service token from a backend, since the key appears in every URL 2. Use the batch geocoding path (up to 50 semicolon-separated queries) rather than one call per address 3. Use api.maptiler.eu when the user's requests must stay in the EU 4. Read docs pages as Markdown by appending .md, starting from https://docs.maptiler.com/llms.txt 5. Don't cache map tiles server-side; the Cloud terms forbid it, though geocoding results may be stored with attribution ## Connect Install: ```bash npm install @maptiler/client ``` First request: ```bash curl "https://api.maptiler.com/geocoding/Zurich.json?language=en&limit=3&key=$MAPTILER_API_KEY" ``` Through letme: https://letme.dev/maptiler. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Mapbox APIs + MCP | BB | 77.2 | 35 | geo.geocode, geo.reverse, geo.places, geo.tiles | no | https://www.anchorterminal.com/tools/mapbox.md | | Amazon Location Service | BB | 76.5 | 43 | geo.geocode, geo.reverse, geo.places, geo.tiles | no | https://www.anchorterminal.com/tools/amazon-location.md | | Google Maps Platform + Grounding Lite MCP | BB | 75.4 | 63 | geo.geocode, geo.reverse, geo.places, geo.tiles | no | https://www.anchorterminal.com/tools/google-maps-platform.md | | Azure Maps | B | 67.1 | 338 | geo.geocode, geo.reverse, geo.places, geo.tiles | no | https://www.anchorterminal.com/tools/azure-maps.md | | ArcGIS Location Platform | B | 66.1 | 380 | geo.geocode, geo.reverse, geo.places, geo.tiles | no | https://www.anchorterminal.com/tools/arcgis.md | | Stadia Maps | B | 65.2 | 431 | geo.geocode, geo.reverse, geo.places, geo.tiles | no | https://www.anchorterminal.com/tools/stadia-maps.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - OpenAPI 3.1.0 reference with 32 paths for the public APIs, and every docs page served as Markdown by appending .md (source: ) - Official agent skill for coding assistants, MIT, first commit 26 February 2026 and last 21 October 2026 (source: ) - EU-only API endpoint api.maptiler.eu added in August 2026, and default API keys converted to restrictable keys the same month (source: ) - The Cloud terms allow bulk download only for the Geocoding API, with attribution, and allow search results to be used outside the service (source: ) - Geocoding index 2.15.25 scheduled for production on 11 November 2026, adding 522,485 map objects from OpenStreetMap (source: ) - ISO/IEC 27001:2022 certified ISMS covering development and cloud operations, per the security page (source: ) - #10 of 18 in Best maps, geocoding and places APIs for AI agents: https://www.anchorterminal.com/best/maps/index.md - All 153 maps comparisons: https://www.anchorterminal.com/compare/maps/index.md ## Compare - [Amazon Location Service vs MapTiler Cloud](https://www.anchorterminal.com/compare/amazon-location-vs-maptiler.md): BB 76.5 vs B 62.1 - [ArcGIS Location Platform vs MapTiler Cloud](https://www.anchorterminal.com/compare/arcgis-vs-maptiler.md): B 66.1 vs B 62.1 - [Azure Maps vs MapTiler Cloud](https://www.anchorterminal.com/compare/azure-maps-vs-maptiler.md): B 67.1 vs B 62.1 - [Geoapify Location Platform + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/geoapify-vs-maptiler.md): C 58.1 vs B 62.1 - [Geocodio vs MapTiler Cloud](https://www.anchorterminal.com/compare/geocodio-vs-maptiler.md): BB 72.2 vs B 62.1 - [Google Maps Platform + Grounding Lite MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/google-maps-platform-vs-maptiler.md): BB 75.4 vs B 62.1 - [HERE Location Services vs MapTiler Cloud](https://www.anchorterminal.com/compare/here-location-services-vs-maptiler.md): C 58.4 vs B 62.1 - [LocationIQ vs MapTiler Cloud](https://www.anchorterminal.com/compare/locationiq-vs-maptiler.md): C 60.3 vs B 62.1 - [Mapbox APIs + MCP vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapbox-vs-maptiler.md): BB 77.2 vs B 62.1 - [MapQuest vs MapTiler Cloud](https://www.anchorterminal.com/compare/mapquest-vs-maptiler.md): F 35.4 vs B 62.1 - [MapTiler Cloud vs NextBillion.ai](https://www.anchorterminal.com/compare/maptiler-vs-nextbillion.md): B 62.1 vs C 55.4 - [MapTiler Cloud vs Nominatim](https://www.anchorterminal.com/compare/maptiler-vs-nominatim.md): B 62.1 vs B 63.5 - [MapTiler Cloud vs OpenCage Geocoding API](https://www.anchorterminal.com/compare/maptiler-vs-opencage.md): B 62.1 vs B 67.5 - [MapTiler Cloud vs Radar](https://www.anchorterminal.com/compare/maptiler-vs-radar.md): B 62.1 vs D 53.3 - [MapTiler Cloud vs Stadia Maps](https://www.anchorterminal.com/compare/maptiler-vs-stadia-maps.md): B 62.1 vs B 65.2 - [MapTiler Cloud vs TomTom Maps APIs + MCP](https://www.anchorterminal.com/compare/maptiler-vs-tomtom.md): B 62.1 vs E 45.9 - [MapTiler Cloud vs Woosmap](https://www.anchorterminal.com/compare/maptiler-vs-woosmap.md): B 62.1 vs C 59.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on maptiler.com or one of its subdomains, or the README at the root of github.com/maptiler/maptiler-client-js. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "maptiler", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html MapTiler Cloud on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![MapTiler Cloud on Anchor Terminal](https://www.anchorterminal.com/badges/maptiler.svg)](https://www.anchorterminal.com/tools/maptiler) ``` Plain link: ```html MapTiler Cloud on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say MapTiler Cloud is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/maptiler-dark.png - Light: https://www.anchorterminal.com/assets/share/maptiler-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp