# Woopra > Woopra is a hosted customer journey and product analytics service from Woopra, Inc., an Appier affiliate. Its HTTP tracking API records events and visitor properties, and its REST API returns saved reports, profiles and raw session logs. - Canonical: https://www.anchorterminal.com/tools/woopra - Markdown: https://www.anchorterminal.com/tools/woopra.md (~7,400 tokens) - Slim: https://www.anchorterminal.com/tools/woopra.min.md (~1,930 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/woopra.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-09 ## Overview **Grade E · 44.4/100 · rank #779 of 842 · #12 in Product analytics & experimentation · not agent-ready · confidence medium** ## Assessment Woopra's REST API returns saved Trends, Journeys, Retention and Attribution reports, profiles and raw session logs, with published limits of 300 calls a minute and 3,000 a day per project. A report must first be built in the web app, the tracking endpoints accept events without a secret by default, and no changelog or SLA was found. ## Facts | Field | Value | | --- | --- | | Vendor | Woopra, Inc. (https://www.woopra.com) | | Kind | HTTP API | | Category | Product analytics & experimentation (https://www.anchorterminal.com/categories/product-analytics) | | Transport | HTTP | | Endpoint | `https://www.woopra.com/rest/3.10` | | Auth | OAuth or key · Self-serve. REST calls use HTTP Basic with an App ID and Secret Key that each user generates on the Access Keys tab of the members area. Tracking calls need only the project name unless the owner enables Secure Tracking, which adds a generated ID and secret sent by HTTP Basic. No OAuth, scopes or partner approval were found in the docs. | | Pricing | Paid ($999 / mo) · Pro starts at $999 a month for 5 million events, with a 30-day trial that an agent's owner can start without a contract. Overage fees apply past the event quota, at rates the pricing page does not state. Enterprise is quoted. Whether the trial signup asks for a card was not established (https://www.woopra.com/pricing, checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the developer docs or on the pricing page (checked 2026-10-09). | | Licence | Proprietary service under Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC | | Packages | npm: `woopra`; npm: `@woopra/browser-tracker` | | Source | https://github.com/Woopra/js-client-tracker | | Docs | https://docs.woopra.com | | llms.txt | https://docs.woopra.com/llms.txt | | Last release | 2026-03-16 | | npm downloads / week | 415 | | Surface graded | The REST API at https://www.woopra.com/rest/3.10 and the HTTP tracking API at https://www.woopra.com/track. No MCP server was found in the docs | | Report endpoints | GET `/trends`, `/journeys`, `/retention`, `/attribution`, `/activity` and `/profiles`, each taking `project` and the `report_id` of a report saved in the web app | | Profile endpoints | GET `/profile` and `/profile/actions` by `key` and `value` (pid, email, id or cookie), POST `/profile/edit` and `/profile/actions/edit`, DELETE `/profile/delete` | | Raw data | GET `/logs/export` by day in Pacific time with `pos` and the `X-Woopra-NextFile` and `X-Woopra-NextPos` response headers. PUT `/logs/import` takes line-separated JSON and returns a batch ID, and GET `/logs/import` reports its status | | Tracking | GET `/track/ce` and `/track/identify` with `project`, `event`, `cookie` and `cv_`, `ce_` and `cs_` prefixed properties. Responses are 200, 202, 401, 402, 403 or 5XX | | Credentials | REST calls use HTTP Basic with a per-user App ID and Secret Key from the Access Keys tab. Tracking needs no secret unless Secure Tracking is on. No OAuth or scopes found | | Rate limits | 300 calls a minute, 600 an hour and 3,000 a day per project on the REST API, with 429 on excess. No limit on tracking calls was found | | Paging | `limit`, `offset` and a `snapshot` ID on report endpoints, with `timeframe_from` and `timeframe_to` in the project's time zone | | Docs for agents | https://docs.woopra.com/llms.txt and a .md copy of each page, with an OpenAPI 3.1 fragment on each REST reference page. No single spec file found | | SDKs | Browser tracker `@woopra/browser-tracker` (tag v5.3.0 of 15 September 2021, last commit 16 March 2026), iOS 1.2.1 and Android 1.1.0 (last commits November 2024), PHP (2023), Node, Python, Java and Rails (2017), all MIT or ISC | | Plans | Pro from $999 a month for 5 million events, 24 months of retention, 50 seats and a 30-day trial. Enterprise by quote with warehouse sync, SSO and data governance. Overage fees apply past the event quota | | Status | status.woopra.com on Atlassian Statuspage with three components (Data Processing, Data Collection, Front-end Application) | | Sub-processors | Amazon Web Services, Atlassian, Cloudflare, Customer.io, Fastly, GitHub, Google Cloud and Intercom in the USA and Hetzner in Germany, per the terms of service | | Legal | Woopra, Inc., San Francisco, with Appier named as affiliate. EU representative Appier Netherlands B.V. California law, or Singapore law for contracts signed with Appier Pte. Ltd. | | Capabilities | analytics.query, analytics.events, analytics.funnels | | Tags | hosted, closed-source, llms-txt, basic-auth, no-oauth, free-trial, status-page, rate-limits, export, sales-led | | JSON | https://www.anchorterminal.com/api/v1/tools/woopra.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 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 | 80 | 16.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 45 | 7.3 | | Agent ergonomics | 13% | 16.2 | 45 | 7.3 | | Security & auth | 14% | 17.5 | 22 | 3.9 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 9 | 0.8 | | Transparency & trust (editorial 45, provenance 77) | 7% | 8.8 | 61 | 5.3 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **44.4 → E** | ### Why each score - Reliability 80: Graded on the REST and HTTP tracking APIs with the hosted lines. Statuspage site at status.woopra.com with three components (20). Its history lists no incidents for August, September or October 2026, the three months shown (30). Limits published with numbers, 300 calls a minute, 600 an hour and 3,000 a day per project (15). A 429 status is documented and tracking calls answer 202 when queued, but no Retry-After, backoff guidance or idempotency key was found (5). No SLA found. The terms promise commercially reasonable efforts (0). The API is version 3.10 with no beta label (10). Total 80. - 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 45: Each REST reference page embeds an OpenAPI 3.1 fragment in its Markdown copy. No single spec file was found, most operations define no responses, and the tracking endpoints are documented as tables (12). llms.txt and a .md copy of each page, though llms.txt lists four of fourteen REST operations (10). Descriptions are one line. The `/profiles` page repeats the `/trends` text, three profile operations have none, and one page still holds template placeholder text (6). Query parameters carry types and required flags. There are no enums, and profile edits take a JSON string in `data` (6). One curl example for REST and several tracking examples. Tracking response codes are explained, while REST errors are a 400 with an empty object (6). The version sits in the path and 3.10 is the only one supported. No changelog found (5). Total 45. - Agent ergonomics 45: Report responses can be capped with `limit`, but a report can only be run from a `report_id` saved in the web app, so an agent can't shape a query through the API (12). `limit`, `offset`, a `snapshot` ID for consistent paging and timeframe overrides on reports, and position headers on log export (14). Tracking codes 401, 402 and 403 each name a cause. REST error bodies are not documented (8). No idempotency key or dedupe field was found, and tracking is by GET. Imports return a batch ID to poll (3). Report calls need two parameters. Official SDKs exist in several languages, but the server ones date from 2017 (8). Total 45. - Security & auth 22: REST calls use per-user access keys sent by HTTP Basic, with no scopes or rotation guidance found. Tracking calls need only the project name by default, with an optional Secure Tracking secret. Docs examples still show `http://` tracking URLs (15 of 30). The pricing page states group and individual permission controls, but no read-only key or confirmation on `/profile/delete` was found (5). The API returns event and profile text that any caller who knows the project name can write, and no guidance on untrusted content was found (0). No audit log found in the docs (0). No security page, bug bounty or certification was found on the pages read, and security.txt timed out. The privacy policy states Data Privacy Framework certification (2). Total 22. - Payments & pricing 30: No x402, MPP or L402 (0). Pro is public at a starting price of $999 a month for 5 million events. Overage rates and Enterprise prices are not published (10). 30-day trial of Pro. The terms say a customer may add a card during the trial, which suggests none is needed to start, but we did not see the signup form (20). A person signs up in a browser and generates keys in the members area (0). Total 30. - 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 9: The newest dated change found is a commit to the browser tracker on 16 March 2026, and the REST intro page was last edited on 13 March 2026, both more than 180 days before the check (0). No releases or dated changelog entries in the last 90 days (0). No API changelog. Support is by email and in-app, and response times were not checked (3). The browser tracker's last tag is v5.3.0 from 2021, iOS and Android were last committed to in November 2024, and the Node, Python, Java and Rails SDKs in 2017 (4). The Node README carries a Travis CI badge and no current CI was found (2). Total 9. - Transparency & trust 61: Closed service with dated terms that cover the subscription, and MIT SDKs (15). The terms say the customer owns tracking data, and the pricing page states 24 months of retention. The privacy policy excludes end-user data, the DPA is sent only on request, and the GDPR page still cites Privacy Shield while the privacy policy cites the Data Privacy Framework (14). No deprecation policy or dated notices found (0). Nine sub-processors named in the terms with addresses and countries, eight in the USA and Hetzner in Germany. Where customer data is stored is not stated (16). Total 45. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/woopra.md (JSON https://www.anchorterminal.com/fixes/woopra.json) ### What we couldn't check - The terms of service list any robot, spider, scraper or other automated means to access the Site among unauthorised activities, and define the Site to include the Services. robots.txt on www.woopra.com allows the pages we read. We found the clause after reading the home, pricing, terms, privacy, GDPR and about pages, and sent no further request to www.woopra.com afterwards. - unchecked: security.txt. https://www.woopra.com/.well-known/security.txt timed out twice with no bytes received. - unchecked: whether the 30-day trial signup asks for a card. The signup form at app.woopra.com was not opened. - unchecked: the members area and web app, including how access keys are revoked, whether a key carries its user's permissions, and any audit log. - unchecked: GitHub stars, open issues and PyPI downloads for the SDKs. - The status page address was not linked from the pages we read. status.woopra.com was tried directly and answered. - No API changelog, deprecation policy, SLA, public DPA, security page or certification was found on the pages read. - Overage rates per event are not on the pricing page. - `lastRelease` is the date of the newest commit to the browser tracker, not a tagged release. The newest tag is v5.3.0 of 15 September 2021. ### Sources - docs index (llms.txt): (seen 2026-10-09) - REST API intro, authentication, rate limits and versioning: (seen 2026-10-09) - HTTP tracking API intro and response codes: (seen 2026-10-09) - /track/ce reference: (seen 2026-10-09) - /trends reference and OpenAPI fragment: (seen 2026-10-09) - /journeys reference: (seen 2026-10-09) - profile delete reference: (seen 2026-10-09) - export API and delete lines: (seen 2026-10-09) - /logs/export reference: (seen 2026-10-09) - /logs/import reference: (seen 2026-10-09) - Secure Tracking: (seen 2026-10-09) - tracking SDKs intro: (seen 2026-10-09) - pricing: (seen 2026-10-09) - terms of service: (seen 2026-10-09) - privacy policy: (seen 2026-10-09) - GDPR page: (seen 2026-10-09) - status page: (seen 2026-10-09) - status history: (seen 2026-10-09) - browser tracker repository: (seen 2026-10-09) - Node SDK repository: (seen 2026-10-09) - npm woopra: (seen 2026-10-09) - npm weekly downloads: (seen 2026-10-09) - RDAP for woopra.com: (seen 2026-10-09) ## Who's behind it (provenance 77/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Woopra, Inc. | 20/20 | | Domain age | woopra.com, registered 2007-02-23 (19 years) | 15/15 | | Endpoint on the vendor's domain | www.woopra.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects | 10/10 | | Status page | status.woopra.com | 10/10 | | Changelog | not found | 0/10 | | security.txt | could not be fetched | 0/10 | The terms of service (last updated 10 December 2025) are a contract with Woopra, Inc., its subsidiaries and affiliated companies including Appier, and cover the website and the subscription services in one document. They give 600 California St, Fl 11, San Francisco, CA 94108 as the legal address. The privacy policy (last updated 1 August 2025) covers customers and site visitors and says it does not apply to end-user data that Woopra processes for customers. It names Appier Netherlands B.V. as EU representative. No public DPA was found, and the GDPR page says a copy is sent on request. The REST and tracking endpoints answer under https://www.woopra.com/rest and https://www.woopra.com/track, on the vendor's own domain. robots.txt on that host disallows both paths, and we sent no request to either. www.woopra.com/.well-known/security.txt timed out twice with no bytes received, so its presence is unknown. status.woopra.com is an Atlassian Statuspage site. Its address was not linked from the pages we read and was tried directly. No changelog for the API was found. docs.woopra.com/changelog returns 404, and the browser tracker's CHANGELOG.md stops at v5.3.0 of 15 September 2021. RDAP for woopra.com gives a registration date of 2007-02-23 and Spaceship, Inc. as registrar. ### 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.woopra.com/tos), read 2026-10-08, dated 2025-12-10, states 6 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "Use any robot, spider, scraper or other automated means to access the Site." - To know. Says access can be ended without notice or for any reason. "Company also reserves the right to terminate these Terms at any time; with or without cause, for any reason or no reason." - To know. Requires arbitration or waives class actions. "(2)THESE TERMS CONTAIN A DISPUTE RESOLUTION AND ARBITRATION AGREEMENT, INCLUDING CLASS ACTION WAIVER, THAT AFFECTS YOUR RIGHTS UNDER THIS AGREEMENT AND WITH RESPECT TO CLAIMS OR DISPUTES YOU MAY HAVE WITH COMPANY." - Gives the date it was last updated. Last updated 2025-12-10. - Names the governing law or courts. The law of California. - States a limit on its liability. Capped at the greater of USD $50 and the fees paid in the 12 months before the claim. - 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-08). Woopra may name the customer in a customer list and in advertising, marketing, promotional and investor materials. "Company may include and use your name on a list of customers and may refer to you as a user of the Services in its advertising, marketing, promotional and investor materials." - Also in the text (2026-10-08). A customer allowed to terminate for convenience must pay the fees that would have been due for the rest of the current term. "you shall pay Company an amount equal to the fees that would have been due over the remainder of the then-current term had these Terms remained in effect" - Also in the text (2026-10-08). The customer owns the Tracking Data, and Woopra purges it on the next deletion cycle after the account is deleted. "When you delete your account, we will purge the Tracking Data on the next data deletion/cleanup cycle." **Privacy policy** (https://www.woopra.com/privacy), read 2026-10-08, dated 2025-08-01, states 8 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2025-08-01. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. privacy@woopra.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. - Also in the text (2026-10-08). The policy covers Woopra's customers and site visitors, and does not apply to data about customers' end users, which Woopra handles as a processor. "This Policy does not apply to the data we process about the end users of our Customers’ services (“End Users”)." ## Live (updated 2026-10-09 09:27 UTC) - Right now: down, HTTP 500, 74 ms, checked 2026-10-09 09:27 UTC (get on `https://www.woopra.com/rest/3.10`) - Uptime 24h 0.0% (20 probes) · 30 days 0.0% (20 probes) · p50 n/a · p95 n/a - Vendor status page: none, All Systems Operational - Always current: https://www.anchorterminal.com/api/v1/live/woopra.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 | | --- | --- | --- | --- | | Pro, 5 million events a month | $999 | per month (plan) | starting price, overage fees apply | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Rate limits are published per project at 300 calls a minute, 600 an hour and 3,000 a day, and limited calls return 429 - Report endpoints take `limit`, `offset`, a `snapshot` ID for consistent paging past 1,000 records, and `timeframe_from` and `timeframe_to` overrides - status.woopra.com (Statuspage) lists no incidents for August, September or October 2026 across Data Processing, Data Collection and the front-end application - `/logs/export` returns raw sessions as line-separated JSON, and `/logs/import` loads them in bulk and returns a batch ID to poll - The terms of service (10 December 2025) name nine sub-processors with addresses and countries, and say the customer owns the tracking data ## Weaknesses - Report endpoints run a report saved in the web app by `report_id`. No endpoint to define a query, funnel or segment was found in the reference - `/track/ce` and `/track/identify` accept data with only the project name unless the owner turns on Secure Tracking - No API changelog, deprecation policy or SLA was found. The terms promise commercially reasonable efforts on availability - Server SDKs are old. The Node, Python, Java and Rails repositories were last committed to in 2017, and npm `woopra` is 1.0.2 - The terms of service forbid using any robot, spider, scraper or other automated means to access the Site, a term defined to include the Services - Most REST operations document no response schema, and the `/profiles` page repeats the `/trends` description ## Before you call it (notes for agents) 1. Ask the owner to build and save each report in the web app first, then pass the last path segment of its URL as `report_id` 2. Authenticate REST calls with HTTP Basic, using the App ID and Secret Key from the Access Keys tab, against `https://www.woopra.com/rest/3.10/` 3. Stay under 300 calls a minute, 600 an hour and 3,000 a day per project. A 429 carries no documented retry interval, so back off on your own schedule 4. Reuse the `snapshot` ID from the first response when paging with `offset`, or pages past 1,000 records may not agree 5. Send `cookie` or a `cv_` identifier such as `cv_email` on every track call. Without one the event lands on a random profile that can't be identified later 6. When reading `/logs/export`, delete the profile named in each `type: "delete"` line. The following lines log its data again under `new_id` ## Connect First request: ```bash curl \ --user : \ "https://www.woopra.com/rest/3.10/trends?project=mybusiness.com&start_day=2017-4-12&end_day=2017-5-19&report_id=83mYcoe6jX" ``` Through letme (picks today, calling later): https://letme.dev/woopra. 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 | | --- | --- | --- | --- | --- | --- | --- | | PostHog | B | 68.4 | 204 | analytics.query, analytics.events, analytics.funnels | no | https://www.anchorterminal.com/tools/posthog.md | | Amplitude | B | 66.2 | 275 | analytics.query, analytics.funnels, analytics.events | no | https://www.anchorterminal.com/tools/amplitude.md | | Fullstory | B | 62.6 | 382 | analytics.query, analytics.events, analytics.funnels | no | https://www.anchorterminal.com/tools/fullstory.md | | Mixpanel | B | 62 | 406 | analytics.query, analytics.funnels, analytics.events | no | https://www.anchorterminal.com/tools/mixpanel.md | | Countly | C | 54.8 | 607 | analytics.query, analytics.events, analytics.funnels | no | https://www.anchorterminal.com/tools/countly.md | | Pendo | D | 48.2 | 729 | analytics.query, analytics.funnels, analytics.events | no | https://www.anchorterminal.com/tools/pendo.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 REST API answers at https://www.woopra.com/rest/3.10 with HTTP Basic authentication, and 3.10 is the only supported version (source: ) - Fourteen REST operations are documented. Six run saved reports (`/trends`, `/journeys`, `/retention`, `/attribution`, `/activity`, `/profiles`), five read, edit or delete a profile, and three export or import raw logs (source: ) - The limit is global per project at 300 calls a minute, 600 an hour and 3,000 a day, described as subject to change (source: ) - Tracking is by GET to `/track/ce` and `/track/identify` with `ce_`, `cv_` and `cs_` prefixed parameters, and answers 200, 202 (queued), 401, 402 (over quota) or 403 (source: ) - Secure Tracking is an optional setting that rejects tracking calls without a generated ID and secret sent by HTTP Basic (source: ) - Pro starts at $999 a month for 5 million events with a 30-day trial, 24 months of retention and 50 seats. Enterprise is quoted (source: ) - The terms of service, last updated 10 December 2025, contract with Woopra, Inc. and affiliates including Appier, and list among unauthorised activities any robot, spider, scraper or other automated means to access the Site (source: ) - docs.woopra.com/llms.txt lists four of the fourteen REST operations and none of the HTTP tracking pages. Each reference page has a Markdown copy with an OpenAPI 3.1 fragment (source: ) ## Compare - [Amplitude vs Woopra](https://www.anchorterminal.com/compare/amplitude-vs-woopra.md): B 66.2 vs E 44.4 - [Countly vs Woopra](https://www.anchorterminal.com/compare/countly-vs-woopra.md): C 54.8 vs E 44.4 - [Fullstory vs Woopra](https://www.anchorterminal.com/compare/fullstory-vs-woopra.md): B 62.6 vs E 44.4 - [GrowthBook vs Woopra](https://www.anchorterminal.com/compare/growthbook-vs-woopra.md): BB 70.1 vs E 44.4 - [Mixpanel vs Woopra](https://www.anchorterminal.com/compare/mixpanel-vs-woopra.md): B 62 vs E 44.4 - [Optimizely Experimentation vs Woopra](https://www.anchorterminal.com/compare/optimizely-vs-woopra.md): B 62.6 vs E 44.4 - [Pendo vs Woopra](https://www.anchorterminal.com/compare/pendo-vs-woopra.md): D 48.2 vs E 44.4 - [PostHog vs Woopra](https://www.anchorterminal.com/compare/posthog-vs-woopra.md): B 68.4 vs E 44.4 - [Statsig vs Woopra](https://www.anchorterminal.com/compare/statsig-vs-woopra.md): BB 72.3 vs E 44.4 - [Heap vs Woopra](https://www.anchorterminal.com/compare/heap-vs-woopra.md): D 53 vs E 44.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on woopra.com or one of its subdomains, or the README of github.com/Woopra/js-client-tracker. 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": "woopra", "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 Woopra on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Woopra on Anchor Terminal](https://www.anchorterminal.com/badges/woopra.svg)](https://www.anchorterminal.com/tools/woopra) ``` Plain link: ```html Woopra on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Woopra 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/woopra-dark.png - Light: https://www.anchorterminal.com/assets/share/woopra-light.png