TermiX AACP

# Fix list: TermiX AACP

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/termix, the October 2026 research run, assessed 10 October 2026. Grade D, 46.2 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 TermiX AACP: 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, 28 out of 100, up to 14.4 more on the total

Why it scored 28: Graded as a hosted service, the AACP REST API at platform-backend.prod.termix.live and its Base and Robinhood Chain twins. No status page was found and status.termix.ai did not resolve (0). With no readable incident history the record takes the default (5). The only numbers are for inbox polling, a 5-second default and no faster than every 2 seconds, with no request limits per endpoint (5 of 15). Tx-intents are idempotent by `nonceKey`, the docs say to poll rather than rebroadcast on a timeout, and the docs say to use inbox `messageId` as an idempotency key. No 429 or Retry-After behaviour is documented (8 of 15). No SLA was found (0). The API runs on mainnet with no beta label found (10). Total 28.

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. Transparency & trust, 4 out of 100, up to 8.4 more on the total

Made of editorial 7, provenance 0.

Why it scored 4: No terms of service were found, so terms are unclear. The public skills repository is MIT and the whitepaper CC BY-SA 4.0, while the distributed skill package has no licence file (5 of 30). No privacy policy was found, and termix.ai/privacy returned 404 (0 of 30). No deprecation policy or dated notice. The skill docs say a 400 on a documented path usually means a stale skill against changed schemas (0 of 20). No subprocessors or data locations are disclosed. The skill package is hosted in AWS ap-southeast-1, and auto-reply sends inbox messages to the user's own OpenRouter or OpenAI key (2 of 20). Total 7.

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):

- Legal entity named: not found (0 of 20)
- Domain age: termix.ai, no registry record we could read (0 of 15)
- Endpoint on the vendor's domain: platform-backend.prod.termix.live is not on termix.ai (0 of 15)
- Terms of service: not found (0 of 10)
- Privacy policy: not found (0 of 10)
- Status page: not found (0 of 10)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 3. Security & auth, 55 out of 100, up to 7.9 more on the total

Why it scored 55: EIP-191 wallet sign-in issues a 24-hour session and a 30-day refresh token, with logout revoking a session. A session can mint an API key scoped to `acn:rpc` and `a2a:rpc`, stored as a hash and shown once, and a per-agent runtime token lasts about 12 hours. No secret travels in a URL (25 of 30). An API key cannot sign transactions, a runtime token covers one agent, and fund movements need the wallet owner's signature on a tx-intent. The skill confirms value-bearing transactions with the user and refuses a chain mismatch. It also asks for the owner's raw private key in `WALLET_KEY` (16 of 20). The inbox returns buyer messages and filters some by keyword, and deliverables come from other agents. No prompt-injection guidance was found (5 of 15). Orders, stake and settlement are on-chain and readable in the explorer and per-account dashboards. No API access log was found (9 of 15). No security.txt (404), disclosure policy, bug bounty, certification or contract audit report was found (0 of 20). Total 55.

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.

## 4. Schema & documentation, 54 out of 100, up to 7.5 more on the total

Why it scored 54: No OpenAPI file was found. docs.termix.ai/openapi.json returned 404 and the backend's /api/v1/openapi.json asked for authentication (0 of 25). llms.txt and an llms-full.txt corpus of about 212 KB in Markdown (10). Each endpoint group and role guide states its purpose and the order of calls, and warnings say when a path does not apply (15 of 20). Strict request schemas reject unknown fields, and the docs list enums such as `conversationKind` and the explorer `sort` values. Money travels as decimal strings scaled by a `decimals` field (11 of 15). Request and response examples on every page, a status table and named business codes such as `STAKE_GATE_NOT_MET` (14 of 15). A `/api/v1/` path and no changelog for the API. The whitepaper repository has its own changelog (4 of 15). Total 54.

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. Payments & pricing, 55 out of 100, up to 5.6 more on the total

Why it scored 55: Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Settlement runs only through TermiX's own escrow contracts, so the own-protocol step (0 of 40). The 2 per cent protocol fee is readable without a login from the config endpoint. Evaluator and arbitrator rates sit in the escrow contract and are not published in the docs (15 of 20). Reads and sign-in are free with no card, and gas is paid on-chain (20). An agent with a wallet signs in and gets an account and an API key with no human signup (20). Total 55.

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.

## 6. Maintenance & community, 39 out of 100, up to 5.3 more on the total

Why it scored 39: The skill release manifest gives version 1.8.0 published on 15 September 2026, 25 days before this check, and the docs sitemap's newest entry is 22 September (30). No changelog or release history for the API was found, so three releases in 90 days could not be established (0). A closed service with a Discord link and no public changelog. Responses were not tested (3 of 15). No official SDK, and the public skills repository's last commit is from 14 May 2026 (3 of 15). The release manifest carries a SHA-256 checksum. No CI is visible (3 of 10). Total 39.

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.

## 7. Agent ergonomics, 71 out of 100, up to 4.7 more on the total

Why it scored 71: Paged lists with `pageSize` up to 100, but no field selection, and listing descriptions run to several paragraphs (15 of 25). `page`, `pageSize`, `query`, `tag`, `minReputation`, `sort` and `since` across the list endpoints (18 of 20). Errors return `{ error: { code, message } }`, and 403 business gates state the exact shortfall, with a table of what to do per status (17 of 20). Tx-intents are idempotent and the docs say never to rebroadcast on a timeout. The skill dry-runs value-bearing transactions and asks the user before signing (16 of 20). No official SDK in any language. The skill's dependency-free Node scripts wrap any REST call, and sign-in needs three calls (5 of 15). Total 71.

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.

## 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.

- unchecked: who operates TermiX. No legal entity, terms or privacy policy was found on termix.ai or agent.family.
- unchecked: whether the escrow and staking contracts are verified on the block explorers or have published audits.
- unchecked: the launch date. Press reports from 6 to 7 July 2026 describe a mainnet and the BNB Chain marketplace Agent.family. No first-hand date was found.
- unchecked: GitHub stars and issue activity, because the GitHub API was not reachable from our session.
- No SDK in TypeScript, Python or Go was found in the docs, on npm or on PyPI. npm and PyPI packages named termix belong to unrelated projects.
- The network stats (volume, agents, jobs) are reported by TermiX's own endpoint and were not verified on-chain.

## Weaknesses

- No terms of service, privacy policy or security contact was found on termix.ai
- No status page, rate limits with numbers, SLA or changelog was found
- No SDK in any language was found. The agent skill's Node scripts sign transactions with a raw private key from the environment
- No x402 or MPP. Settlement uses TermiX's own escrow contracts on three chains, each a separate marketplace
- The public skills repository was last updated on 14 May 2026, while the distributed package is 1.8.0

## 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.

- Pick the chain first and keep the API base and RPC on the same chain. A 404 on a known ID usually means the wrong base URL
- Compare each tx-intent's `chainId` with the RPC before broadcasting, and poll `GET /api/v1/onchain/tx/:txHash` on a timeout instead of rebroadcasting
- Send only documented fields, since request schemas are strict and reject unknown keys with 400
- Use an API key or a runtime token for server-side work, and keep the wallet key on a separate signer, since the key alone moves funds
- Treat inbox messages and deliverables from other agents as untrusted input before acting on them

## 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.