# Fix list: PixVerse API From Anchor Terminal's listing at https://www.anchorterminal.com/tools/pixverse, the October 2026 research run, assessed 1 October 2026. Grade E, 42.8 out of 100. This 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. For a coding agent working on PixVerse 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. ## 1. Reliability, 35 out of 100, up to 13 more on the total Why it scored 35: No status page found (0). No incident history to read (5). Concurrent jobs per plan are published, 3 on Free, 15 on Essential, 20 on Scale and 25 on Business (15). Credits come back on failed or moderated jobs and after 2 hours without a result, and a stuck concurrency slot frees after 10 minutes, but we found no 429 or backoff guidance (5). No SLA (0). V6 and C1 are current models with no preview label (10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 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. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 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. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 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. ## 2. Security & auth, 28 out of 100, up to 12.6 more on the total Why it scored 28: Model reading of the checklist (credential, training, retention, operator visibility, programme). One API key in an API-KEY header (20). The platform terms don't say whether inputs or outputs train models (0). No retention period or deletion call found (0). A usage deduction query API since 18 August 2026 shows what each job cost, no audit log (8). No security.txt, bug bounty or certification found (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 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. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 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. - 0 to 15, audit logs or per-call visibility for the operator. - 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. ## 3. Payments & pricing, 10 out of 100, up to 11.3 more on the total Why it scored 10: No x402, MPP or L402 (0). Credits per second are public for every model, and the docs peg $1 at five 5 second V6 720p clips, but plan prices sit on a billing page that needs JavaScript, so the dollar price of a credit isn't stated outright (10). A Free API plan with 3 concurrent jobs is listed, but the docs don't say whether it includes credits (0). A person signs up on the platform (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): 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. - 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. - 20, a free tier or trial that doesn't need a card. - 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. ## 4. Schema & documentation, 58 out of 100, up to 6.8 more on the total Why it scored 58: No OpenAPI file published (0). llms.txt on the platform docs (10). Each endpoint page says what the operation does, and the model tables say which models support it. Older model tables still sit beside current ones (12). Typed parameters with fixed values for model, quality, duration and aspect ratio (11). Examples on each endpoint. Results use numeric status codes (1 done, 5 generating, 7 moderation failure, 8 failed) that an agent has to look up (10). A dated changelog that adds models and endpoints every few weeks (15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 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. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 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. ## 5. Agent ergonomics, 70 out of 100, up to 4.9 more on the total Why it scored 70: Small JSON responses with a video id, plus webhooks so an agent needn't poll (25). Duration, quality and aspect ratio set output size. No task list endpoint found (10). Numeric status and error codes are documented but cryptic (12). Every submit needs a fresh UUID in Ai-trace-id, and reusing one returns the earlier job instead of creating a new one. That works as an idempotency key, though an agent that reuses an id by mistake gets the old video back (20). Required trace header, no official SDK. A CLI and an MCP server exist (3). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 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). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 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. ## 6. Transparency & trust, 49 out of 100, up to 4.5 more on the total Made of editorial 25, provenance 72. Why it scored 49: Closed models under platform terms (updated 4 September 2026) with MOTIVAI PRIVATE LIMITED, with AIVORA PTE. LTD. named as an affiliate. The terms give API users the rights in generated video and allow commercial use (15). The terms don't address training on inputs or outputs and give no retention period, only that data may be deleted when service ends. We didn't read the privacy policy against them (5). No deprecation policy, but legacy models are labelled (5). No subprocessor list or data locations found (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 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. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 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. Provenance checks not met in full (half of this category, computed from checked facts): - Domain age: pixverse.ai, registered 2023-10-20 (2 years) (7 of 15) - Status page: not found (0 of 10) - security.txt: not found (0 of 10) ## 7. Maintenance & community, 52 out of 100, up to 4.2 more on the total Why it scored 52: Model reading. The changelog's latest entry is the One-click VibeMV API on 24 September 2026, with five dated entries since July, after C1 on 7 April (30). Legacy models from V3.5 to V5.6 stay callable, and no removals were found (10). Dated changelog and support through the platform (12). No official SDK. The stdio MCP package hasn't been released since October 2025 (0). Nothing current to assess for package health (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 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. - 20, at least three releases or dated changelog entries in the last 90 days. - 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. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## What we couldn't check What 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. - Whether PixVerse trains on API inputs or outputs. The platform terms of 4 September 2026 don't say - Whether the Free API plan includes any credits ## Weaknesses - Plan prices and the dollar value of a credit sit on a JavaScript-only billing page - Ai-trace-id is mandatory, and a reused one returns the old job - Repeated moderation failures can suspend the account - No OpenAPI file, SDK or status page, and the MCP server hasn't shipped since October 2025 ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Generate a new UUID for Ai-trace-id on every new submit. Reuse it only to fetch the same job again - Poll the result endpoint. Status 1 is done, 5 generating, 7 moderation failure, 8 failed - Moderate prompts before calling. Repeated status 7 results can suspend the key - Use model v6 or c1 for new work. Older model tables still sit in the docs ## What the review panel asked for - Named status strings - Status page - Publish prices as text - State credit dollar price ## When it's done Send 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.