{
  "fixes": {
    "slug": "mubert",
    "name": "Mubert API",
    "listing": "https://www.anchorterminal.com/tools/mubert",
    "markdown": "# Fix list: Mubert API\n\nFrom Anchor Terminal's listing at https://www.anchorterminal.com/tools/mubert, the October 2026 research run, assessed 1 October 2026. Grade E, 41.3 out of 100.\n\nThis is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.\n\nFor a coding agent working on Mubert API: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.\n\n## 1. Reliability, 30 out of 100, up to 14 more on the total\n\nWhy it scored 30: No status page found (0). No readable incident history (5). Quotas published with numbers, monthly generations and streaming minutes per plan (100, 5,000 and 30,000) plus per-customer daily caps and concurrency in the licence object (15). No 429 or retry guidance in the docs (0). No SLA (0). API v3 isn't labelled beta (10).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):\n\nHosted APIs, MCP servers, models and platforms.\n\n- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.\n\nLocal packages, SDKs, frameworks and stdio MCP servers.\n\n- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.\n\nProtocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.\n\n## 2. Payments \u0026 pricing, 10 out of 100, up to 11.3 more on the total\n\nWhy it scored 10: No x402, MPP or L402 on the API or MCP server (0). Plan prices are public, $49, $199 and $499 a month, with no per-call price (10). No free API tier. The free tier mentioned in llms.txt is for Mubert Render, not the API (0). Credentials arrive by email after a checkout (0).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):\n\nThe published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).\n\n- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.\n- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for \"contact sales\" or prices behind a login.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).\n\nPayment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.\n\nOpen-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.\n\n## 3. Security \u0026 auth, 45 out of 100, up to 9.6 more on the total\n\nWhy it scored 45: Two credential tiers, a company licence token for service routes and per-customer access tokens for public routes, and OAuth 2.1 with PKCE on the hosted MCP. Stream URLs carry the customer access token, so a secret travels in a URL by design (30 less 10, 20). Per-customer tokens with daily caps keep one end user from spending a whole licence (10). Returns generated audio and Mubert's own library metadata, no untrusted content (10). Licence responses report quota use per customer, with no per-call log found (5). No security.txt, disclosure policy, bug bounty or certification found (0).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-security):\n\n- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.\n\nModels are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.\n\n## 4. Agent ergonomics, 42 out of 100, up to 9.4 more on the total\n\nWhy it scored 42: 21 MCP tools, in the 11 to 30 band, with no toolsets or read-only subset found (15). Webhooks for generation status from the Startup plan, and a library search to try before generating (15). No error codes or messages documented (0). No idempotency key. The listing's check found the MCP server checks quota before spending, which we couldn't re-read today (5). Sensible defaults and pre-rendered durations, no SDK beyond an agent skill and the MCP server (7).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):\n\n- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.\n\nModels are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.\n\n## 5. Schema \u0026 documentation, 69 out of 100, up to 5 more on the total\n\nWhy it scored 69: OpenAPI document for v3 at music-api.mubert.com, plus a hosted MCP server (25). llms.txt (10). The docs explain the licence, customer and track flows and when a pre-rendered duration returns in one request. We couldn't read the MCP tool descriptions themselves (12). Typed inputs with a fixed list of pre-rendered durations (5 to 300 seconds), `intensity`, `mode` and `format` enums and a `playlist_index` (12). Request and response examples, but only 200 and 204 documented, no error codes (5). Versioned `/api/v3` path, no changelog (5).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):\n\nAPIs and MCP servers.\n\n- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.\n\nModels are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.\n\n## 6. Transparency \u0026 trust, 45 out of 100, up to 4.8 more on the total\n\nMade of editorial 20, provenance 70.\n\nWhy it scored 45: Closed service. The terms and llms.txt say plainly that Mubert Inc owns generated music and grants a licence to use it, and list where it can't go (artist releases on Spotify or Apple Music, Content ID, stock marketplaces) (15). We couldn't read the privacy policy on 2026-10-01, so no retention or training statements were checked (5). No deprecation policy or dated notices found (0). No subprocessor list or data locations found, and the terms and contact page give different Delaware addresses (0).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):\n\n- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).\n\nThe other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.\n\nProvenance checks not met in full (half of this category, computed from checked facts):\n\n- Status page: not found (0 of 10)\n- Changelog: not found (0 of 10)\n- security.txt: not found (0 of 10)\n\n## 7. Maintenance \u0026 community, 48 out of 100, up to 4.6 more on the total\n\nWhy it scored 48: The hosted MCP server entered the official registry on 2026-09-28, per the listing's check of 2026-09-30 (30). No changelog, so no count of releases in the last 90 days (0). No public changelog and no community channel found (3). Listed in the official MCP registry under the verified `com.mubert` namespace (15). Hosted service, and the agent-skill repo on GitHub has no stars or issues to judge (0).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):\n\n- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.\n\nModels are read for deprecation notice periods and model churn rather than release counts.\n\n## What we couldn't check\n\nWhat we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.\n\n- We couldn't read the MCP tool definitions or the registry entry on 2026-10-01, so the tool count (21), the quota check before spending and the 2026-09-28 registry date rest on the listing's check of 2026-09-30.\n- The privacy policy didn't load for us today, so retention and training statements are unchecked.\n- Whether 429s are returned when quotas run out, or another status.\n\n## Weaknesses\n\n- Mubert Inc owns generated tracks, and the licence excludes artist releases, Content ID and stock marketplaces\n- No free API tier. Entry plan is $49 a month for 100 generations\n- No status page, changelog, error codes or security.txt\n- Stream URLs carry an access token, and vocals and stems need a custom plan\n\n## What costs an agent a turn today\n\nThe notes we give agents before they call it. Each one is a workaround an agent shouldn't need.\n\n- Search the library before generating. A match costs no generation\n- Pick a pre-rendered duration (5, 6, 8, 10, 15, 20, 30, 40, 60, 180, 240 or 300 seconds) for a one-request result\n- Download tracks straight away. URLs expire after 900 seconds by default\n- Treat stream URLs as secrets. They carry the customer access token\n\n## What the review panel asked for\n\n- Documented error codes\n- Self-serve credentials\n- Add free API tier\n\n## When it's done\n\nSend what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `\"kind\": \"dispute\"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.\n",
    "grade": "E",
    "score": 41.3,
    "assessed": "2026-10-01",
    "run": "October 2026 research run",
    "categories": [
      {
        "key": "reliability",
        "name": "Reliability",
        "score": 30,
        "maxGain": 14,
        "reason": "No status page found (0). No readable incident history (5). Quotas published with numbers, monthly generations and streaming minutes per plan (100, 5,000 and 30,000) plus per-customer daily caps and concurrency in the licence object (15). No 429 or retry guidance in the docs (0). No SLA (0). API v3 isn't labelled beta (10).",
        "checklist": [
          "Hosted APIs, MCP servers, models and platforms.",
          "- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.",
          "Local packages, SDKs, frameworks and stdio MCP servers.",
          "- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.",
          "Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-reliability"
      },
      {
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "score": 10,
        "maxGain": 11.3,
        "reason": "No x402, MPP or L402 on the API or MCP server (0). Plan prices are public, $49, $199 and $499 a month, with no per-call price (10). No free API tier. The free tier mentioned in llms.txt is for Mubert Render, not the API (0). Credentials arrive by email after a checkout (0).",
        "checklist": [
          "The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).",
          "- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.\n- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for \"contact sales\" or prices behind a login.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).",
          "Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.",
          "Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-payments"
      },
      {
        "key": "security",
        "name": "Security \u0026 auth",
        "score": 45,
        "maxGain": 9.6,
        "reason": "Two credential tiers, a company licence token for service routes and per-customer access tokens for public routes, and OAuth 2.1 with PKCE on the hosted MCP. Stream URLs carry the customer access token, so a secret travels in a URL by design (30 less 10, 20). Per-customer tokens with daily caps keep one end user from spending a whole licence (10). Returns generated audio and Mubert's own library metadata, no untrusted content (10). Licence responses report quota use per customer, with no per-call log found (5). No security.txt, disclosure policy, bug bounty or certification found (0).",
        "checklist": [
          "- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.",
          "Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-security"
      },
      {
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "score": 42,
        "maxGain": 9.4,
        "reason": "21 MCP tools, in the 11 to 30 band, with no toolsets or read-only subset found (15). Webhooks for generation status from the Startup plan, and a library search to try before generating (15). No error codes or messages documented (0). No idempotency key. The listing's check found the MCP server checks quota before spending, which we couldn't re-read today (5). Sensible defaults and pre-rendered durations, no SDK beyond an agent skill and the MCP server (7).",
        "checklist": [
          "- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.",
          "Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-ergonomics"
      },
      {
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "score": 69,
        "maxGain": 5,
        "reason": "OpenAPI document for v3 at music-api.mubert.com, plus a hosted MCP server (25). llms.txt (10). The docs explain the licence, customer and track flows and when a pre-rendered duration returns in one request. We couldn't read the MCP tool descriptions themselves (12). Typed inputs with a fixed list of pre-rendered durations (5 to 300 seconds), `intensity`, `mode` and `format` enums and a `playlist_index` (12). Request and response examples, but only 200 and 204 documented, no error codes (5). Versioned `/api/v3` path, no changelog (5).",
        "checklist": [
          "APIs and MCP servers.",
          "- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.",
          "Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-schema"
      },
      {
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "score": 45,
        "maxGain": 4.8,
        "reason": "Closed service. The terms and llms.txt say plainly that Mubert Inc owns generated music and grants a licence to use it, and list where it can't go (artist releases on Spotify or Apple Music, Content ID, stock marketplaces) (15). We couldn't read the privacy policy on 2026-10-01, so no retention or training statements were checked (5). No deprecation policy or dated notices found (0). No subprocessor list or data locations found, and the terms and contact page give different Delaware addresses (0).",
        "blend": "editorial 20, provenance 70",
        "checklist": [
          "- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).",
          "The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-transparency"
      },
      {
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "score": 48,
        "maxGain": 4.6,
        "reason": "The hosted MCP server entered the official registry on 2026-09-28, per the listing's check of 2026-09-30 (30). No changelog, so no count of releases in the last 90 days (0). No public changelog and no community channel found (3). Listed in the official MCP registry under the verified `com.mubert` namespace (15). Hosted service, and the agent-skill repo on GitHub has no stars or issues to judge (0).",
        "checklist": [
          "- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.",
          "Models are read for deprecation notice periods and model churn rather than release counts."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-maintenance"
      }
    ],
    "provenance": [
      {
        "label": "Status page",
        "value": "not found",
        "points": 0,
        "max": 10
      },
      {
        "label": "Changelog",
        "value": "not found",
        "points": 0,
        "max": 10
      },
      {
        "label": "security.txt",
        "value": "not found",
        "points": 0,
        "max": 10
      }
    ],
    "unchecked": [
      "We couldn't read the MCP tool definitions or the registry entry on 2026-10-01, so the tool count (21), the quota check before spending and the 2026-09-28 registry date rest on the listing's check of 2026-09-30.",
      "The privacy policy didn't load for us today, so retention and training statements are unchecked.",
      "Whether 429s are returned when quotas run out, or another status."
    ],
    "weaknesses": [
      "Mubert Inc owns generated tracks, and the licence excludes artist releases, Content ID and stock marketplaces",
      "No free API tier. Entry plan is $49 a month for 100 generations",
      "No status page, changelog, error codes or security.txt",
      "Stream URLs carry an access token, and vocals and stems need a custom plan"
    ],
    "agentNotes": [
      "Search the library before generating. A match costs no generation",
      "Pick a pre-rendered duration (5, 6, 8, 10, 15, 20, 30, 40, 60, 180, 240 or 300 seconds) for a one-request result",
      "Download tracks straight away. URLs expire after 900 seconds by default",
      "Treat stream URLs as secrets. They carry the customer access token"
    ],
    "requests": [
      {
        "text": "Documented error codes",
        "reviews": 1
      },
      {
        "text": "Self-serve credentials",
        "reviews": 1
      },
      {
        "text": "Add free API tier",
        "reviews": 1
      }
    ],
    "recheck": "https://www.anchorterminal.com/builders/#disputes"
  },
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-04",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.3",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  }
}