APITemplate.io

# Fix list: APITemplate.io

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/apitemplate-io, the October 2026 research run, assessed 9 October 2026. Grade D, 46.6 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 APITemplate.io: 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. Payments & pricing, 30 out of 100, up to 8.8 more on the total

Why it scored 30: No x402, MPP or L402 (0). Plan prices with monthly file counts are public without a login, and no per-file or overage rate is published (10). Free plan of 50 files a month with no card (20). A person signs up in a browser to get the key (0). Total 30.

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.

## 2. Agent ergonomics, 49 out of 100, up to 8.3 more on the total

Why it scored 49: Responses are short JSON with download URLs, `export_type` chooses bytes or JSON, and `with_layer_info` is off by default (15). `limit` and `offset` on both list operations with filters by template, type, format and group. The default page is 300 records (15). Errors are a `status` and `message` pair with no codes or recovery guidance (6). No idempotency key. A `meta` reference shows in `list-objects`, which lets a caller check before retrying, and deletion is a GET request (4). Only `template_id` is required and calls are synchronous by default. The five SDK repositories are generated clients from September 2023 with placeholder install commands (9). Total 49.

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.

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

Why it scored 53: One API key per account, regenerable in the console, with a separate key per team (20). The Direct URL `auth` code travels in a query string by design. It is tied to one template with a quota and an expiry and is not the API key, so we took no 10-point deduction. That is a judgement call. No scopes or read-only key, and `delete-object` runs on a GET with no confirmation. The Direct URL code is the only narrow credential (5). Calls return status and URLs, not third-party content (10). Request logs kept two weeks, visible in the console and switchable off, and `list-objects` records the caller's IP address (8). The site states a completed SOC 2 Type II audit with no auditor, period or report shown, plus a security policy page and 2FA. No security.txt (404), disclosure policy or bug bounty found (10). Total 53.

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, 52 out of 100, up to 7.8 more on the total

Why it scored 52: A public OpenAPI 3.0.0 description of 12 operations, linked from the REST guide. It needed a tab character replaced before a strict YAML reader accepted it, and it carries slips such as `type: int` (22). No llms.txt (404) and no Markdown docs for agents (0). Parameter descriptions state defaults and interactions, while operation descriptions are one line and say nothing on when to use each (11). Flags are strings holding `1` or `0`, 3 of 31 shared parameters carry enums, and the image `overrides` body is an open object (5). Request samples in five languages and examples on 26 of 31 shared parameters, but errors are one generic object with no status codes (9). A `/v2` path with the v1 reference still online, and no changelog (5). Total 52.

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. Maintenance & community, 11 out of 100, up to 7.8 more on the total

Why it scored 11: No changelog or release notes exist. The API description file was last modified on 28 September 2026 by its HTTP header, which is file metadata and not a dated release, so the recency line scores 0. No dated changelog entries in the last 90 days (0). Support by email with a stated reply within 24 hours and response times in the SLA, with no public changelog (6). Five SDK repositories, each a generated client committed once on 17 September 2023 (3). No tags, CI results or licence files in those repositories (2). Total 11.

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.

## 6. Reliability, 65 out of 100, up to 7 more on the total

Why it scored 65: Hosted lines. Status page at status.apitemplate.io, hosted by UptimeRobot (20). Its 90-day figures load by script from a path the page's robots.txt disallows, so the history was not read and takes the unreadable-history score (5). Rate limits are published as 100 requests per 10 seconds per IP address and 100 concurrent synchronous PDF requests per account (15). HTTP 429 is documented with advice to pause before retrying, but no `Retry-After`, backoff interval or idempotency key (5). The SLA page commits to 99.9 per cent monthly availability with service credits (10). The generation API is generally available, with `get-template`, `update-template` and the e-invoice option marked experimental (10). Total 65.

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.

## 7. Transparency & trust, 59 out of 100, up to 3.6 more on the total

Made of editorial 58, provenance 59.

Why it scored 59: Closed service under terms of use dated 8 April 2022, which can change without prior notice. The SDK repositories have no licence file (13). Privacy policy dated 21 January 2024 and a public DPA with standard contractual clauses. Request logs are kept two weeks, account data is deleted within 30 days of cancellation, and free accounts' files are purged after one year. Retention of personal data is otherwise stated only as long as reasonably needed (22). Clause 15.8 of the terms promises 60 days' written notice before a service is withdrawn, while clause 2.24 reserves the right to modify or discontinue any part with or without notice. No dated deprecation notices found (6). Eleven sub-processors named with purpose and country, 14 days' notice of new ones in the DPA, and four storage regions listed (17). Total 58.

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: apitemplate.io, no registry record we could read (0 of 15)
- Terms of service: read, states 6 of the 7 things a reader expects, and has 2 clauses that cost points (5.1 of 10)
- Privacy policy: read, states 6 of the 8 things a reader expects (8.5 of 10)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## Deductions

Each comes off the total. A fixed and documented problem counts for less at the next check.

- 2026-10-09. Two vendor documentation pages disagree on regional endpoints. The first-request guide (https://apitemplate.io/docs/getting-started/first-api-request) lists `rest.apitemplate.io` as the US default with `rest-eu` and `rest-sg` hosts. The API reference and REST guide (https://apitemplate.io/docs/integrations/rest-api) list it as the Singapore default with `rest-de` and `rest-us`. The vendor says data is processed and stored in the region of the endpoint, so the conflict affects data residency. We did not test which hostnames resolve. 2 points.

## 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: the status page's 90-day uptime and incident history, which loads by script from a path its robots.txt disallows
- unchecked: which regional hostnames resolve. The guides and the API reference disagree, and we sent no request to an API host
- unchecked: the SOC 2 Type II report, its auditor and period. The site states the audit and shows no document
- unchecked: the v1 API reference and template language pages on docs.apitemplate.io, whose robots.txt answered 403. We read no page on that host
- unchecked: the domain's registration date. rdap.org answered 404
- unchecked: GitHub stars and issue response on the SDK repositories, and whether any SDK is published to npm, PyPI or Packagist
- The terms of use forbid any robot, spider or other automatic device accessing the Site or Service (clause 8.1) and allow suspension for load or vulnerability testing without agreement (clause 15.4). No deduction taken. Settle this with the vendor before any probe is run
- Whether failed generations count against the monthly quota, and the overage rate on Enterprise plans
- Whether the Direct URL `auth` code should take the checklist's 10-point deduction for a secret in a query string. We took none
- The API description file sits on an Amazon S3 host with no robots.txt (the request for it answered 403). We read the file once, as the docs link it

## Weaknesses

- One API key per account or team with no scopes or read-only mode, and `GET /v2/delete-object` deletes a file with a GET request
- No changelog, release notes or dated deprecation notices were found, and the terms allow the service to change with or without notice
- The five SDK repositories each hold a generated client committed on 17 September 2023, with no tags, no licence file and placeholder install commands
- The first-request guide names `rest-eu` and `rest-sg` hostnames and a US default, while the API reference names `rest-de` and `rest-us` and a Singapore default
- Errors are documented as one `status` and `message` object with no status codes listed, and no idempotency key exists for generation calls
- The terms of use forbid any robot or other automatic device accessing the Site or Service, and bar load or vulnerability testing without agreement. This matters before any probe is run

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

- Send the key in the `X-API-KEY` header and pick the regional host first, because requests and output are processed and stored in that region
- Call `GET /v2/list-templates` with `with_layer_info=1` before `POST /v2/create-image`, so the `name` values in `overrides` match the template's elements
- Set `meta` to your own reference on each generation and check `GET /v2/list-objects` before retrying, since there is no idempotency key
- Set `expiration` in minutes (1 to 10080) or `export_type=file` for sensitive output. By default the download URL does not expire
- For `async=1` you must pass `webhook_url`. The callback is a GET with the result in the query string, retried three times
- On HTTP 429 pause and retry on your own schedule. The docs give no `Retry-After` header or backoff interval

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