# Zeal > Zeal is an embedded payroll API for US staffing platforms, labour marketplaces and workforce software. Partners create employer companies, onboard W-2 employees and 1099 contractors, create pay cheques and contractor payments, preview payroll and pull reports. - Canonical: https://www.anchorterminal.com/tools/zeal - Markdown: https://www.anchorterminal.com/tools/zeal.md (~7,350 tokens) - Slim: https://www.anchorterminal.com/tools/zeal.min.md (~1,930 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/zeal.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-08 ## Overview **Grade E · 45.4/100 · rank #569 of 629 · #5 in Payroll infrastructure · not agent-ready · confidence medium** ## Assessment Graded on the partner REST API at api.zeal.com, which is the only access route. Three OpenAPI specs, llms.txt, a test environment that moves no money, a preview endpoint and a per-cheque approval flag are documented. Access starts with a demo request, prices are not published, each environment has one unscoped key, and no status page or working changelog was found. ## Facts | Field | Value | | --- | --- | | Vendor | Puzzl Group Inc. (https://www.zeal.com) | | Kind | HTTP API | | Category | Payroll infrastructure (https://www.anchorterminal.com/categories/payroll) | | Transport | HTTP | | Endpoint | `https://api.zeal.com` | | Auth | API key · API keys, issued only to Zeal partners. Zeal's team creates the partner account after a demo request, then the Partner Dashboard at app.zeal.com shows one Test API key, one Production API key and the `partnerID`. Every call sends `Authorization: Bearer {apiKey}`, and most also need a `companyID`. A key covers every employer company under the partner, has no scopes, and is rolled from the dashboard, which invalidates the old key at once. Production payroll is switched on by Zeal (error code 0 until then). The agent chat and MCP endpoints need a key that Zeal has Agent-enabled. This is embedded-payroll partner access. An employer has no separate API route into its own Zeal payroll account. | | Pricing | Paid (Paid) · No public prices. www.zeal.com/pricing returns 404 and every call to action asks for a demo. A test environment that moves no money exists, but its key comes only after Zeal creates a partner account, so an agent cannot start without a sales contact. No free tier or self-serve trial was found (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in llms-full.txt, the OpenAPI specs or the marketing site (checked 2026-10-08). | | Licence | Proprietary service. The npm SDK declares MIT. The SDK repositories on GitHub carry no licence file | | Packages | npm: `@zeal-api/sdk`; pypi: `zeal-api-sdk` | | Source | https://github.com/zeal-corp/typescript-sdk | | Docs | https://docs.zeal.com | | llms.txt | https://docs.zeal.com/llms.txt | | Last release | 2026-07-31 | | GitHub stars | 0 (as of 2026-10-08) | | npm downloads / week | 8 | | Access route graded | Embedded-payroll partnership. A software platform becomes a Zeal partner and holds the keys for every employer company it creates. Zeal has no API for an employer to reach an existing payroll account of its own outside a partner | | API | REST at https://api.zeal.com with no version in the path, JSON in and out. The main OpenAPI 3.1 spec has 128 paths and 177 operations (91 POST, 58 GET, 19 PATCH, 8 DELETE, 1 PUT) | | Environments | Test and Production, each with its own key and separate data. Test processes payroll with no money moved and no tax filings. Responses carry `testMode` | | Credentials | One Test API key and one Production API key per partner account, sent as a Bearer token, rolled from the API page of the Partner Dashboard. No scopes | | Preview and approval | POST /preview/checks, /preview/checkDate and /preview/checkData start a job, GET /preview returns the breakdown. `approval_required` on a cheque or contractor payment blocks processing until `approved` is true | | Rate limits | 100 requests a second in both modes, then 429. The error page recommends exponential backoff. No Retry-After header is documented | | Idempotency | `x-idempotency-key` request header, honoured for 24 hours, in both modes | | Pagination | Cursor with `start_at` and `limit` on some list endpoints, with `meta.next` and `meta.previous` links. Not every endpoint pages | | Errors | `{success:false, errors:[{message, code}]}` with 116 numbered codes mapped to HTTP statuses. An unauthenticated call returned a `correlationId` on 8 October 2026 | | Webhooks | 27 reference pages covering company, employee, contractor, cheque, payment, shift, report job, paperwork, bank account and garnishment events. URLs are set per event in the dashboard. `Puzzl-Signature` carries the shared secret | | SDKs | @zeal-api/sdk 0.2.1 on npm (30 July 2026, MIT) and zeal-api-sdk 0.2.1 on PyPI (31 July 2026), both generated with Fern. The docs site does not mention them | | Agents and MCP | The spec lists POST /agents/chat and an MCP Streamable HTTP endpoint at /mcp with four tools (ask_PayrollSpecialistAgent, ask_HrSpecialistAgent, ask_ReportingSpecialistAgent, ask_MigrationsSpecialistAgent). Both need an Agent-enabled key that Zeal's team switches on. No guide page found | | Coverage | United States only, all 50 states. W-2 employees and 1099 contractors. Zeal says it files and pays payroll taxes and issues W-2 and 1099 forms | | Early Access | Endpoints marked Early Access (I-9, custom paperwork, paycards, customer accounts, employee requirements) are enabled per partner contract | | Security claims | SOC 2 Type II, AWS hosting, TLS 1.2 in transit and AES-256 at rest, per the security tab of zeal.com/legal. No report or trust centre is linked | | Capabilities | payroll.run, payroll.embedded, payroll.employees, payroll.contractors, payroll.tax-filing, hr.onboarding | | Tags | hosted, api-key, openapi, llms-txt, typescript, python, webhooks, sandbox, sales-led, partner-only, us-only, soc2, mcp | | JSON | https://www.anchorterminal.com/api/v1/tools/zeal.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 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 | 42 | 8.4 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 68 | 11.1 | | Agent ergonomics | 13% | 16.2 | 63 | 10.2 | | Security & auth | 14% | 17.5 | 34 | 6.0 | | Payments & pricing | 10% | 12.5 | 0 | 0.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 61 | 5.3 | | Transparency & trust (editorial 38, provenance 64) | 7% | 8.8 | 51 | 4.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **45.4 → E** | ### Why each score - Reliability 42: Read with the hosted rubric, on the partner REST API. No status page found. None is linked from the site, the docs or the help centre, and status.zeal.com did not complete a TLS handshake on 8 October 2026 (0). With no page there is no readable incident history (5). The rate limit is published as 100 requests a second in both Test and Production (15). The error page recommends exponential backoff on 429 and an `x-idempotency-key` header is honoured for 24 hours, but no Retry-After header is documented (12 of 15). No SLA found on the public site (0). The core REST API is generally available. Endpoints marked Early Access and the agent and MCP endpoints are enabled per partner (10). Total 42. - 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 68: Three public OpenAPI 3.1 specs at docs.zeal.com/openapi, the main one with 128 paths and 177 operations (25). docs.zeal.com/llms.txt, llms-full.txt (514 KB) and a Markdown copy of every page (10). 99 of 177 operations carry a description, 18 have no summary and 5 are titled "Copy of", and pages rarely say when not to use an endpoint (10 of 20). 359 `required` lists and 120 enums, with 212 of 228 parameters described, against 82 objects with no declared properties and string-typed dates (10 of 15). 2,088 examples in the spec and a table of 116 numbered error codes with HTTP statuses. 429 is not declared in the spec (13 of 15). The API has no version in the path or a header, the spec version is a fixed 1.0, and the changelog URL the site links to returns 404 (0). Total 68. - Agent ergonomics 63: Responses can't be trimmed by field. `limit` is on a few list endpoints and one webhook has a lite form with IDs only (8 of 25). Cursor pagination with `start_at`, `limit` and `meta.next`, on some endpoints only, with filters by company, employee, date and status (10 of 20). Errors come as `{message, code}` with 116 documented codes, several of which name the fix, such as code 89 for a date past the 2 PM cut-off (17 of 20). `x-idempotency-key` for 24 hours on writes, and the SDKs retry 408, 429 and 5xx twice with backoff. The spec declares the header nowhere (16 of 20). TypeScript and Python SDKs at 0.2.1, generated with Fern and not mentioned in the docs. Most calls need both `companyID` and, at partner level, `partnerID`, and previews and reports are asynchronous jobs (12 of 15). Total 63. - Security & auth 34: One Test key and one Production key per partner account, sent as a Bearer header, rollable from the dashboard with the old key invalidated at once. A key reaches every employer company under the partner and has no scopes, so we scored between one all-powerful key and plain revocable keys (15 of 30). No read-only key. `approval_required` holds a cheque or contractor payment until `approved` is set, and the Test environment moves no money (8 of 20). The API returns names, addresses and metadata written by workers and employers, and the agent and MCP endpoints return model-written text, with no guidance on untrusted content found (3 of 15). No audit log or per-call log was found in the docs (0). The legal page states SOC 2 Type II, AWS hosting, TLS 1.2 and AES-256, with no report, trust centre, disclosure policy, bounty or security.txt (8 of 20). Total 34. - Payments & pricing 0: Read with the hosted rubric. No x402, MPP or L402 (0). No price is published. www.zeal.com/pricing returns 404 and the site asks for a demo (0). No free tier or self-serve trial. Test keys exist only after Zeal's team creates a partner account (0). A person has to contact sales and log in to the Partner Dashboard for a key (0). Total 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 61: With the changelog returning 404, the newest dated public release is the Python SDK zeal-api-sdk 0.2.1 on 31 July 2026, 69 days before the check (20 of 30). npm shows @zeal-api/sdk 0.1.0, 0.2.0 and 0.2.1 on 28, 29 and 30 July 2026, three releases inside 90 days, all in one week (20). A closed service with a help centre and support@zeal.com, and no working public changelog or community channel (5 of 25). Official SDKs in two languages, both at 0.2.1 and not referenced by the docs (12 of 15). The SDK repositories hold tests and a Dependabot branch but no CI workflow, and the Python package declares no licence (4 of 10). Total 61. - Transparency & trust 51: Editorial half only. A closed service. The public terms are a website Terms of Use and Payroll Terms between Puzzl Group Inc. and a partner's client. The partner agreement is not public (12 of 30). The privacy notice, last updated 16 January 2026, keeps data as long as necessary with no periods, lists vendor categories only, and still gives a privacy@joinpuzzl address in one place. The Payroll Terms let Puzzl use aggregate or de-identified data for its own purposes. No DPA found (12 of 30). One dated deprecation, the `garnishment` deduction type with a sunset of 15 October 2026, and no written policy (8 of 20). AWS hosting and Bangor Savings Bank are named. No sub-processor list or data location statement found (6 of 20). Total 38. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/zeal.md (JSON https://www.anchorterminal.com/fixes/zeal.json) ### What we couldn't check - unchecked: whether status.zeal.com is a live status page. It did not complete a TLS handshake from our network, and no status link was found on the site - unchecked: weekly downloads for zeal-api-sdk on PyPI. pypistats returned no data - The tools, schemas and annotations behind the /mcp endpoint. The spec names four tools and says access needs an Agent-enabled key from Zeal - Prices, any SLA and the partner agreement, none of which are public - Whether the Partner Dashboard keeps an audit log of API calls - The date of the last API change. The changelog URL returns 404 and the API root shows only a build hash - Whether Zeal has a SOC 2 report or sub-processor list available under NDA ### Sources - API introduction, base URL, environments and error format: (seen 2026-10-08) - Authentication, key rolling and webhook secret: (seen 2026-10-08) - Rate limiting: (seen 2026-10-08) - Idempotency: (seen 2026-10-08) - Pagination: (seen 2026-10-08) - Error codes: (seen 2026-10-08) - Early Access endpoints: (seen 2026-10-08) - Account setup and API keys: (seen 2026-10-08) - Introduction to payroll runs: (seen 2026-10-08) - Preview payroll guide: (seen 2026-10-08) - FAQs (coverage, tax engine, year-end forms): (seen 2026-10-08) - Main OpenAPI spec, including /mcp and /agents/chat: (seen 2026-10-08) - Docs index for agents: (seen 2026-10-08) - Full docs text: (seen 2026-10-08) - Changelog URL (404): (seen 2026-10-08) - Home page and navigation: (seen 2026-10-08) - Marketing llms.txt (RTF): (seen 2026-10-08) - Legal page with privacy, security, terms and payroll terms: (seen 2026-10-08) - Pricing URL (404): (seen 2026-10-08) - security.txt (404): (seen 2026-10-08) - Help centre: (seen 2026-10-08) - API root and unauthenticated response: (seen 2026-10-08) - TypeScript SDK repository: (seen 2026-10-08) - Python SDK repository: (seen 2026-10-08) - npm registry entry: (seen 2026-10-08) - PyPI entry: (seen 2026-10-08) - Domain registration (RDAP): (seen 2026-10-08) - Official MCP registry search: (seen 2026-10-08) ## Who's behind it (provenance 64/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Puzzl Group Inc. | 20/20 | | Domain age | zeal.com, registered 1995-07-03 (31 years) | 15/15 | | Endpoint on the vendor's domain | api.zeal.com | 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 | not found | 0/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | The legal page names Puzzl Group Inc., a Delaware corporation, 80 Langton Street, San Francisco, CA 94103. Its privacy notice was last updated on 16 January 2026. The API answers at https://api.zeal.com and docs at docs.zeal.com (hosted on Mintlify). The help centre at support.zeal.com runs on Pylon. www.zeal.com/.well-known/security.txt and docs.zeal.com/.well-known/security.txt return 404. No status page is linked from the site, the docs or the help centre. status.zeal.com did not complete a TLS handshake on 8 October 2026. The changelog URL the site advertises, https://docs.zeal.com/changelog, returns 404, so the field is left empty. The legal page says banking services come from Bangor Savings Bank, Member FDIC. RDAP for zeal.com gives a registration date of 1995-07-03 and GoDaddy.com, LLC 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.zeal.com/legal?tab=terms-of-service), read 2026-10-08, dated 2026-01-16, states 6 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "(viii) attempt to access or search the Software or download content from the Software using any engine, software, tool, agent, device or mechanism (including spiders, robots, crawlers, data mining tools or the like)" - To know. Says the terms or the service can change without notice (costs points). "Because the Services are evolving over time, Puzzl or Partner may change or discontinue all or any part of the Services, at any time and without notice, at Puzzl’s or Partner’s sole discretion." - Gives the date it was last updated. Last updated 2026-01-16. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - 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). Liability for breach of the service agreement is limited to the greater of the additional charges assessed against the client or 1,000 US dollars, plus tax interest or penalties caused by the breach. "(I) FOR PUZZL TO REMIT TO THE APPROPRIATE PAYEE OF CLIENT THE GREATER OF: (A) THE AMOUNT OF ADDITIONAL CHARGES ASSESSED AGAINST CLIENT UNDER THIS AGREEMENT OR (B) ONE THOUSAND ($1,000) U.S. DOLLARS;" - Also in the text (2026-10-08). The client grants an irrevocable licence under which Puzzl may compile aggregate or de-identified data from Client Data and use it for its own purposes. "(ii) compile and use for Puzzl’s own purposes aggregate or de identified data, statistics, measurements or other metrics derived from Client Data and Client’s use of the Services, which do not identify Client or Client’s Employees (“Aggregate Data”)." - Also in the text (2026-10-08). The client irrevocably permits Puzzl to use the client's signature on file for tax filings, administrative filings and corrections, and Puzzl is not obliged to tell the client when it does. "While Puzzl will use commercially reasonable efforts to inform Client of such permitted usage of Client’s signature on file, Client agree that company is not obligated to do so." **Privacy policy** (https://www.zeal.com/legal?tab=privacy-policy), read 2026-10-08, dated 2026-01-16, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-01-16. - Says how long data is kept. For as long as needed, with no period named. - Gives a privacy contact. privacy@zeal.com. - Not found in the text. Says where data is transferred or stored. - Also in the text (2026-10-08). After a request to end an account, Zeal deactivates or deletes it from active databases but may keep some information for fraud prevention, troubleshooting, investigations, enforcement and legal requirements. "However, we may retain some information in our files to prevent fraud, troubleshoot problems, assist with any investigations, enforce our Terms of Use and/or comply with applicable legal requirements." - Also in the text (2026-10-08). The notice states that the website is for residents of the United States only. "This website is for US residents only." ## Live (updated 2026-10-08 17:36 UTC) - Right now: up, HTTP 200, 626 ms, checked 2026-10-08 17:36 UTC (get on `https://api.zeal.com`) - Uptime 24h 100.0% (25 probes) · 30 days 100.0% (25 probes) · p50 585 ms · p95 700 ms - npm `@zeal-api/sdk` 0.2.1 - pypi `zeal-api-sdk` 0.2.1, released 2026-07-31 - security.txt: none - Always current: https://www.anchorterminal.com/api/v1/live/zeal.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. ## Strengths - Public OpenAPI 3.1 specs with 177 operations, plus llms.txt, llms-full.txt and a Markdown copy of every docs page - Test keys run payroll end to end with no money moved and no tax filings, in an environment separate from production - Preview endpoints return the gross-to-net breakdown before processing, and `approval_required` holds a cheque until `approved` is set - `x-idempotency-key` header honoured for 24 hours, and 116 numbered error codes with messages - Fern-generated TypeScript and Python SDKs (0.2.1, July 2026) that retry 408, 429 and 5xx with backoff ## Weaknesses - No self-serve signup. Zeal's team creates the partner account after a demo request, and no price is published - One test key and one production key per partner account, with no scopes and no read-only key - No status page found, and the changelog linked from the home page and llms.txt returns 404 - The API has no version in the path or a header, and the main spec has 18 operations with no summary - Webhooks carry the shared secret itself in `Puzzl-Signature`, not a signature of the payload - No security.txt, disclosure policy, sub-processor list or DPA found on the public site ## Before you call it (notes for agents) 1. Use the Test API key until a person has approved live payroll. Error code 0 (403) means the account has no production access 2. Send `companyID` on almost every call and `partnerID` on partner-level calls, in the body for POST and PATCH and the query for GET 3. Create cheques with `approval_required: true`, run POST /preview/checks, then PATCH /employeeCheck with `approved: true`. Without the flag Zeal processes pending cheques automatically 4. Send `x-idempotency-key` on every create so a retry within 24 hours doesn't pay twice 5. Previews and reports are jobs. Keep the `job_id` and poll GET /preview or GET /reports, or wait for the Job Queue webhook 6. Check dates must be bank days and submitted before 2 PM Pacific two bank days ahead, or the call fails with code 89 ## Connect Install: ```bash npm i -s @zeal-api/sdk ``` First request: ```bash curl --request GET \ --url 'https://api.zeal.com/companies?partnerID=YOUR_PARTNER_ID' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer YOUR_API_KEY' ``` Through letme (picks today, calling later): https://letme.dev/zeal. 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 | | --- | --- | --- | --- | --- | --- | --- | | Gusto | B | 63.3 | 283 | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors, hr.onboarding | no | https://www.anchorterminal.com/tools/gusto.md | | Check | B | 67.5 | 193 | payroll.run, payroll.employees, payroll.embedded, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/check-payroll.md | | Salsa | D | 46.1 | 565 | payroll.run, payroll.embedded, payroll.employees, payroll.tax-filing, payroll.contractors | no | https://www.anchorterminal.com/tools/salsa.md | | Finch | BB | 71.6 | 99 | payroll.employees, payroll.contractors | no | https://www.anchorterminal.com/tools/finch.md | | Deel | B | 69.1 | 158 | hr.onboarding | no | https://www.anchorterminal.com/tools/deel.md | | BambooHR | C | 61.7 | 319 | hr.onboarding | no | https://www.anchorterminal.com/tools/bamboohr.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 - Access is by partnership. The setup guide says to contact Zeal to create a Partner Account, and Zeal's integration team leads the setup (source: ) - Test keys process payroll end to end with no money moved and no real tax filings (source: ) - Zeal processes pending cheques automatically before the cheque date unless `approval_required` is set and the cheque is left unapproved (source: ) - The spec at docs.zeal.com/openapi/zeal-api.json lists an MCP Streamable HTTP endpoint at /mcp and POST /agents/chat, both gated on an Agent-enabled API key (source: ) - The changelog linked from the home page and from www.zeal.com/llms.txt returned 404 on 8 October 2026 (source: ) - www.zeal.com/llms.txt is served as an RTF document with RTF control codes, while docs.zeal.com/llms.txt is plain Markdown (source: ) - The `garnishment` deduction type is marked deprecated with a sunset of 15 October 2026 in favour of the Garnishments API (source: ) ## Compare - [Check vs Zeal](https://www.anchorterminal.com/compare/check-payroll-vs-zeal.md): B 67.5 vs E 45.4 - [Gusto vs Zeal](https://www.anchorterminal.com/compare/gusto-vs-zeal.md): B 63.3 vs E 45.4 - [Salsa vs Zeal](https://www.anchorterminal.com/compare/salsa-vs-zeal.md): D 46.1 vs E 45.4 - [Finch vs Zeal](https://www.anchorterminal.com/compare/finch-vs-zeal.md): BB 71.6 vs E 45.4 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on zeal.com or one of its subdomains, or the README of github.com/zeal-corp/typescript-sdk. 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": "zeal", "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 Zeal on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Zeal on Anchor Terminal](https://www.anchorterminal.com/badges/zeal.svg)](https://www.anchorterminal.com/tools/zeal) ``` Plain link: ```html Zeal on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Zeal 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/zeal-dark.png - Light: https://www.anchorterminal.com/assets/share/zeal-light.png