# Terra API > Terra's Unified API collects activity, sleep, body and nutrition data from 500+ wearables and health apps, normalises it into one schema and sends it by webhook or REST. An MCP server, Terra AI, lets agents read a connected user's data. - Canonical: https://www.anchorterminal.com/tools/terra - Markdown: https://www.anchorterminal.com/tools/terra.md (~7,050 tokens) - Slim: https://www.anchorterminal.com/tools/terra.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/terra.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-14 ## Overview **Grade B · 65.9/100 · rank #327 of 1076 · #2 in Health records & wellness data · not agent-ready · confidence medium** ## Assessment Graded on the Unified API and the Terra AI MCP server. A public OpenAPI 3.1 spec, llms.txt, per-user rate limits with Retry-After, and scoped admin tokens with approvals. Access starts at $499 a month with billing details at sign-up, the data API key has no scopes, and API key requests failed for 2 hours 38 minutes on 7 August 2026. ## Facts | Field | Value | | --- | --- | | Vendor | Terra Enabling Developers Inc. (https://tryterra.co) | | Kind | HTTP API | | Category | Health records & wellness data (https://www.anchorterminal.com/categories/health-data) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://access.tryterra.co/api/v2/mcp/` | | Auth | OAuth or key · A self-serve dashboard account gives a dev-id and one x-api-key per environment, sent as headers to the Unified API and to Terra AI. The key has no scopes and can be rotated. The admin API and admin MCP server take personal access tokens with 26 scopes, lifetimes of 7 to 90 days and optional environment limits. The admin MCP server signs in by OAuth, and risky changes need approval in the dashboard. End users connect each wearable through Terra's widget, and Terra holds the provider tokens. | | Pricing | Pay per use ($499 / mo) · Quick Start from $499 a month includes 100,000 credits, then $0.005 a credit to 1,000,000 and $0.003 above. Sign-up asks for a plan and billing details, with a 30-day money-back guarantee and no free tier found. Testing and staging environments allow 50 users each. Enterprise is custom (checked 2026-10-14). | | x402 | No · No x402, MPP or L402 in the docs, the OpenAPI specs or the pricing page (checked 2026-10-14). | | Licence | Proprietary service under Terra's terms of service. The OpenAPI specs repository is Apache 2.0 | | Tools exposed | 6 | | Packages | pypi: `terra-python`; npm: `terra-api`; npm: `@tryterra/cli` | | Source | https://github.com/tryterra/openapi | | Docs | https://docs.tryterra.co | | llms.txt | https://docs.tryterra.co/llms.txt | | Last release | 2026-10-13 | | npm downloads / week | 13,061 | | PyPI downloads / week | 10,636 | | APIs | Unified API v2 (OpenAPI 3.1, 55 operations, version 2026.10.08.1), Streaming API (AsyncAPI), Teams API, Vantage API, admin API (101 operations), all in github.com/tryterra/openapi | | MCP servers | Terra AI at https://access.tryterra.co/api/v2/mcp/, six read tools, dev-id and x-api-key headers. Admin server at https://access.tryterra.co/api/v3/admin/mcp, OAuth with client ID metadata documents, no dynamic client registration | | Credentials | Unified API and Terra AI take dev-id plus one x-api-key per environment (testing, staging, production). Admin API and admin MCP take personal access tokens with 26 scopes, 7 to 90 day lifetimes and optional environment limits | | Rate limits | Per user, 1,825 days per request window and 6,000 requested days per UTC hour bucket on data-read endpoints. 429 carries X-Terra-RateLimit-Rule and Retry-After for the hourly rule | | Errors | application/problem+json with code and detail, for example 401 `unauthorized` and 403 `scope_missing`. Terra AI documents guaranteed error strings for transport and tool failures | | Environments | Testing and staging capped at 50 users each, production unlimited | | Pricing | Quick Start from $499 a month with 100,000 credits. Extra credits $0.005 to 1,000,000 and $0.003 above. 200 credits per active authentication a month, first 400 events per authentication free then 0.5 credits each. Model runs 1 credit ($0.01). Enterprise custom with BAA and SLAs | | SDKs | terra-python 1.1.0 and terra-api 2.1.0 on npm (2 October 2025), Terra CLI @tryterra/cli 0.20.0 (9 October 2026), mobile SDKs for iOS, Android, React Native and Flutter. The legacy JavaScript package no longer receives updates | | Status | status.tryterra.co on Instatus, groups for 78 data providers and Terra infrastructure, with incident history and RSS | | Certifications | SOC 2 Type II, HIPAA and GDPR claimed on tryterra.co. The Vanta trust centre is drawn by script and was not read | | Capabilities | health.wearables, health.consent, health.fhir | | Tags | hosted, wearables, health-data, mcp, api-key, openapi, llms-txt, webhooks, status-page, python, typescript, soc2, hipaa | | JSON | https://www.anchorterminal.com/api/v1/tools/terra.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-14 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 | 67 | 13.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 89 | 14.5 | | Agent ergonomics | 13% | 16.2 | 78 | 12.7 | | Security & auth | 14% | 17.5 | 65 | 11.4 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 75 | 6.6 | | Transparency & trust (editorial 42, provenance 69) | 7% | 8.8 | 56 | 4.9 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **65.9 → B** | ### Why each score - Reliability 67: Read with the hosted lines and scored on the Unified API and Terra AI. status.tryterra.co on Instatus has components and incident history (20). In the 90 days to 14 October 2026 Terra's own REST endpoints failed with authorisation errors for 2 hours 38 minutes on 7 August, and a large share of data requests errored for 16 minutes on 29 September. Provider-side incidents (Garmin since 1 September, Fitbit, TrainerRoad) are outside Terra's API. One major outage (10). Per-user limits published with numbers (15). 429 carries Retry-After and a rule header with backoff code. No idempotency keys for writes, though dedupe guidance is published (12 of 15). No SLA outside Enterprise contracts (0). The Unified API carries no beta label (10). - 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 89: OpenAPI 3.1 specs in tryterra/openapi for the Unified, admin, Teams, Vantage and widget APIs, plus AsyncAPI for streaming (25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Operation descriptions state purpose, and some say when to use another path, such as the deprecated token route (16 of 20). The Unified spec has 173 required lists but only 18 enums (10 of 15). 573 examples and problem+json error responses, plus a guaranteed error list for Terra AI (13 of 15). Dated spec versions, monthly changelog pages and date-based versioning on Vantage (15). - Agent ergonomics 78: Terra AI has six tools, each taking an explicit fields or select list, which keeps responses small. The admin server has about 40 tools, filtered by access level (22 of 25). Date ranges, with_samples and to_webhook size the REST reads, with no cursor paging since bulk data goes to webhooks (14 of 20). problem+json errors carry a code, 403 names scope_missing, and 429 names the rule (17 of 20). No idempotency keys. The admin server has dry runs and dashboard approval for risky changes (12 of 20). user_id is the main required parameter, with Python and npm SDKs and a CLI, though both SDKs date from October 2025 (13 of 15). - Security & auth 65: The data API key is one x-api-key per environment with no scopes, rotatable through the admin API. Admin tokens have 26 scopes, 7 to 90 day lifetimes, environment limits and revocation, and the admin MCP server uses OAuth. No secret in a query string (22 of 30). Read only access for the admin server, dashboard approval for paying invoices, rotating keys or removing members, and Terra AI is read-only (18 of 20). Health data is mostly numeric, and the MCP page warns that text in payloads can mislead an assistant (8 of 15). Token list with creation source and an event log, no API call audit log found (7 of 15). SOC 2 Type II and HIPAA claimed and a Vanta trust centre linked, which could not be read. No security.txt or bug bounty found (10 of 20). - Payments & pricing 20: Read with the hosted rubric. No x402, MPP or L402 (0). Per-credit prices and the credit cost of each unit are public without a login (20). No free tier. Sign-up asks for a plan and billing details, with a 30-day money-back guarantee (0). A person signs up in a browser, and the CLI and MCP sign in through the dashboard (0). - 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 75: The OpenAPI repository was republished on 13 October 2026 and @tryterra/cli 0.20.0 shipped on 9 October (30). 120 spec publishes since 16 July and CLI releases 0.18 to 0.20 in October (20). Closed service with monthly changelog pages and a support form. 24/7 engineering support is Enterprise only (11 of 15). terra-python 1.1.0 and terra-api 2.1.0 date from 2 October 2025, the legacy JavaScript package is no longer updated, and the official MCP registry has no Terra entry (8 of 15). We could not read CI results (6 of 10). - Transparency & trust 56: Closed service with public terms dated 1 May 2026 and Apache 2.0 specs (17 of 30). The privacy policy, effective 20 April 2023, excludes end-user wearable data and gives no fixed retention periods. A GDPR assessment sits in the trust centre, which could not be read, and no public DPA was found (10 of 30). A deprecated token route is kept indefinitely and Vantage changes ship under dated versions, with no written notice period for the Unified API (10 of 20). Processing is stated as mainly in the UK, with no sub-processor list found (5 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (17 items): https://www.anchorterminal.com/fixes/terra.md (JSON https://www.anchorterminal.com/fixes/terra.json) ### What we couldn't check - unchecked: the Vanta trust centre at app.vanta.com/tryterra.co/trust. It is drawn by script and our reader saw only the title, so the SOC 2 report and any sub-processor list were not read - unchecked: live API behaviour beyond two unauthenticated requests, which returned 401 problem+json. We had no credentials - unchecked: GitHub stars and CI for the tryterra repositories. The GitHub API refused us for rate limits - unchecked: the registration date of tryterra.co. RDAP returned no events - No idempotency key was found for the write endpoints (nutrition, body, planned workouts) - The founder's lead named the product Terra API at tryterra.co, which matches. Terra also runs Vantage, Lab Reports and Models APIs, graded here only as part of the platform ### Sources - documentation index for agents: (seen 2026-10-14) - account set-up and API keys: (seen 2026-10-14) - Terra AI MCP server: (seen 2026-10-14) - Terra AI error states: (seen 2026-10-14) - admin MCP server: (seen 2026-10-14) - personal access tokens: (seen 2026-10-14) - token scopes: (seen 2026-10-14) - rate limits: (seen 2026-10-14) - environments: (seen 2026-10-14) - credit pricing: (seen 2026-10-14) - pricing page: (seen 2026-10-14) - OpenAPI specs: (seen 2026-10-14) - September 2026 changelog: (seen 2026-10-14) - Vantage versioning: (seen 2026-10-14) - status history feed: (seen 2026-10-14) - terms of service: (seen 2026-10-14) - privacy policy: (seen 2026-10-14) - GDPR page: (seen 2026-10-14) - enterprise page (certifications): (seen 2026-10-14) - npm terra-api: (seen 2026-10-14) - npm @tryterra/cli: (seen 2026-10-14) - PyPI terra-python: (seen 2026-10-14) - unauthenticated API request: (seen 2026-10-14) - official MCP registry search: (seen 2026-10-14) ## Who's behind it (provenance 69/100, checked 2026-10-14) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Terra Enabling Developers Inc. | 20/20 | | Domain age | tryterra.co, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | access.tryterra.co | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points | 5.1/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.tryterra.co | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms of service, last updated 1 May 2026, are between the customer and Terra Enabling Developers Inc., a Delaware corporation. The privacy policy names a UK subsidiary, Terra Enabling Developers Ltd. The privacy policy (effective 20 April 2023) says it doesn't cover data collected from wearables about end users, and that processing takes place mainly in the United Kingdom. tryterra.co/.well-known/security.txt returns 404. RDAP for tryterra.co returned no registration date. API and MCP endpoints answer at access.tryterra.co, a tryterra.co subdomain. ### 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://tryterra.co/terms-of-service), read 2026-10-14, dated 2026-05-01, states 6 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "publicly disseminate information from any source regarding the performance of the Services or Output; or (vi) attempt to create a competitive, substitute or similar service through use of, or access to, the Services or Output" - To know. Says the terms or the service can change without notice (costs points). "Terra may modify the terms of this Agreement at any time by posting the revised version on its website or notifying Customer by email, and such changes will become effective upon posting or on the date specified in the notice." - To know. Says access can be ended without notice or for any reason. "…has passed a previous Compliance Review or received provisional access to the Services), Terra may suspend, revoke, or terminate Customer's access to the Services, without notice or liability to Customer.1.8 Responsible Use.Customer agrees to use the Services and the API Package responsibly." - To know. Requires arbitration or waives class actions. "This Agreement contains mandatory arbitration provisions that require the use of arbitration to resolve disputes." - Gives the date it was last updated. Last updated 2026-05-01. - Names the governing law or courts. The law of the State of Delaware. - States a limit on its liability. Capped at the fees paid in the 6 months before the claim or one hundred dollars. - Says how changes to the terms are announced. Says it gives notice of a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-14). Terra may revise its rates or pricing structure at any time. "Terra may revise its rates or pricing structure for the Services at any time" - Also in the text (2026-10-14). The customer agrees to take part in case studies and other marketing Terra reasonably requests, and Terra may disclose it as a customer. "During the term of this Agreement, (a) Customer agrees to participate in case studies and other similar marketing efforts reasonably requested by Terra; (b) Terra may disclose that Customer is a Terra customer to third parties" **Privacy policy** (https://tryterra.co/privacy), read 2026-10-14, dated 2023-04-20, states 7 of the 8 things a reader expects. - To know. Has not been updated for three years or more. "Effective Date: 20th April 2023" - Gives the date it was last updated. Last updated 2023-04-20. - Says how long data is kept. For as long as needed, with no period named. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. privacy@tryterra.coLegal. - Also in the text (2026-10-14). The policy does not cover data Terra collects from wearables about end users. "This Policy does not cover data we collect from wearables about end users." ## Live (updated 2026-10-14 09:42 UTC) - Right now: up, HTTP 401, 45 ms, checked 2026-10-14 09:42 UTC (get on `https://access.tryterra.co/api/v2/mcp/`, asks for auth) - Uptime 24h 100.0% (17 probes) · 30 days 100.0% (17 probes) · p50 47 ms · p95 126 ms - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/terra.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 | | --- | --- | --- | --- | | Quick Start plan, 100,000 credits included | $499 | per month (plan) | From price on tryterra.co/pricing, 2026-10-14 | | Credit beyond the monthly allowance (100,001 to 1,000,000) | $0.005 | per credit | $0.003 above 1,000,000 credits. An active user costs 200 credits a month | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.1 specs on GitHub under Apache 2.0, republished almost daily (spec version 2026.10.08.1 for the Unified API) - Rate limits documented per user, with a Retry-After header and an X-Terra-RateLimit-Rule header naming the rule that fired - Terra AI MCP server has six read tools that take explicit fields or select lists, so an agent fetches only the columns it needs - Admin tokens carry 26 scopes, expire within 90 days, can be limited to environments, and risky changes need approval in the dashboard - Credit prices are public, $0.005 a credit from 100,001 to 1,000,000 and $0.003 above, with 200 credits per active user a month ## Weaknesses - No free tier. Sign-up asks for a plan and billing details, and Quick Start starts at $499 a month with a 30-day money-back guarantee - The Unified API key is one environment-wide x-api-key with no scopes, and Terra AI takes the same key - status.tryterra.co shows REST requests failing with authorisation errors for 2 hours 38 minutes on 7 August 2026 - No SLA is published outside Enterprise contracts, and no idempotency keys were found for write endpoints - The privacy policy, effective 20 April 2023, excludes end-user wearable data, and no public sub-processor list was found ## Before you call it (notes for agents) 1. Send dev-id and x-api-key headers on every Unified API and Terra AI call. A missing header returns 401 problem+json 2. Keep each request window to 1,825 days or less and under 6,000 requested days per user an hour. On 429 with rule r2, wait Retry-After seconds 3. Pass either fields or select to Terra AI tools, never both and never neither, or the call fails with a validation error 4. Expect data by webhook after a user connects through the widget session. REST reads are for backfills and on-demand queries 5. Use the Read only access level for the admin MCP server unless a change is needed. The MCP level can read API keys ## Connect Claude Code: ```bash claude mcp add --transport http terra-ai https://access.tryterra.co/api/v2/mcp/ --header "dev-id: " --header "x-api-key: " ``` MCP client configuration: ```json { "mcpServers": { "terra-ai": { "headers": { "dev-id": "YOUR_DEV_ID", "x-api-key": "YOUR_API_KEY" }, "url": "https://access.tryterra.co/api/v2/mcp/\u003cuser_id\u003e" } } } ``` Through letme (picks today, calling later): https://letme.dev/terra (letme picks it for health.consent, the top-graded tool for the job, letme picks it for health.wearables, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. 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 | | --- | --- | --- | --- | --- | --- | --- | | ROOK | C | 54.9 | 718 | health.wearables, health.consent, health.fhir | no | https://www.anchorterminal.com/tools/rook.md | | Aidbox | B | 64.2 | 385 | health.fhir, health.consent | no | https://www.anchorterminal.com/tools/aidbox.md | | Health Gorilla | C | 59.3 | 583 | health.fhir, health.consent | no | https://www.anchorterminal.com/tools/health-gorilla.md | | Validic Inform | C | 57.9 | 628 | health.wearables, health.consent | no | https://www.anchorterminal.com/tools/validic.md | | Zus Health | C | 56.6 | 669 | health.fhir, health.consent | no | https://www.anchorterminal.com/tools/zus-health.md | | Medblocks | D | 52.7 | 773 | health.consent, health.fhir | no | https://www.anchorterminal.com/tools/medblocks.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 - The Unified API answers at https://access.tryterra.co/api/v2 with dev-id and x-api-key headers, per the OpenAPI spec in tryterra/openapi (source: ) - Terra AI is a remote MCP server at https://access.tryterra.co/api/v2/mcp/ with six tools, get_sleep_data, get_activity_data, get_daily_data, get_body_data, get_nutrition_data and get_menstruation_data (source: ) - A separate admin MCP server at https://access.tryterra.co/api/v3/admin/mcp manages the account over OAuth, with Read only and MCP access levels, dry runs and dashboard approval for risky changes (source: ) - Rate limits apply per user, 1,825 days per request and 6,000 requested days per rolling hour bucket, with Retry-After on 429 (source: ) - status.tryterra.co lists a 2 hour 38 minute window on 7 August 2026 when API key requests failed with authorisation errors, and 16 minutes of errors on 29 September 2026 (source: ) - The website terms say Terra is SOC 2 Type II certified and HIPAA and GDPR compliant, with a Vanta trust centre linked from the GDPR page (source: ) - #2 of 12 in Best health record and wellness data APIs for AI agents: https://www.anchorterminal.com/best/health-data/index.md - All 63 health comparisons: https://www.anchorterminal.com/compare/health-data/index.md ## Compare - [1upHealth vs Terra API](https://www.anchorterminal.com/compare/1uphealth-vs-terra.md): D 46.8 vs B 65.9 - [Aidbox vs Terra API](https://www.anchorterminal.com/compare/aidbox-vs-terra.md): B 64.2 vs B 65.9 - [Health Gorilla vs Terra API](https://www.anchorterminal.com/compare/health-gorilla-vs-terra.md): C 59.3 vs B 65.9 - [Medplum vs Terra API](https://www.anchorterminal.com/compare/medplum-vs-terra.md): B 68.7 vs B 65.9 - [Metriport Medical API vs Terra API](https://www.anchorterminal.com/compare/metriport-vs-terra.md): D 50.1 vs B 65.9 - [Particle Health vs Terra API](https://www.anchorterminal.com/compare/particle-health-vs-terra.md): D 48.6 vs B 65.9 - [Redox vs Terra API](https://www.anchorterminal.com/compare/redox-vs-terra.md): C 58.3 vs B 65.9 - [Medblocks vs Terra API](https://www.anchorterminal.com/compare/medblocks-vs-terra.md): D 52.7 vs B 65.9 - [Terra API vs Zus Health](https://www.anchorterminal.com/compare/terra-vs-zus-health.md): B 65.9 vs C 56.6 - [ROOK vs Terra API](https://www.anchorterminal.com/compare/rook-vs-terra.md): C 54.9 vs B 65.9 - [Terra API vs Validic Inform](https://www.anchorterminal.com/compare/terra-vs-validic.md): B 65.9 vs C 57.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on tryterra.co or one of its subdomains, or the README of github.com/tryterra/openapi. 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": "terra", "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 Terra API on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Terra API on Anchor Terminal](https://www.anchorterminal.com/badges/terra.svg)](https://www.anchorterminal.com/tools/terra) ``` Plain link: ```html Terra API on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Terra API 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/terra-dark.png - Light: https://www.anchorterminal.com/assets/share/terra-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=terra