Natura tinyNature

# Fix list: Natura tinyNature

From Anchor Terminal's listing at https://www.anchorterminal.com/tools/natura, the October 2026 research run, assessed 12 October 2026. Grade F, 15.1 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 Natura tinyNature: 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, 15 out of 100, up to 17 more on the total

Why it scored 15: Read with the hosted lines, on tinyNature. No status page found, and status.natura.inc doesn't resolve (0). No readable incident history (5). No limits published, and no interface for an outside agent (0). No overload or retry guidance (0). No SLA (0). tinyNature answers on iMessage, WhatsApp and Telegram today and isn't labelled beta. Only the Interface ring is waitlist only (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. Agent ergonomics, 0 out of 100, up to 16.3 more on the total

Why it scored 0: Graded on the interface an outside agent can use. tinyNature has none, so context cost, pagination, errors, retries and defaults have nothing to score (0 on each line). This says nothing about the agent for people.

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

Why it scored 10: Graded on the interface an outside agent can use. With none for tinyNature, the credential, least-privilege, injection and audit lines score nothing (0 of 30, 0 of 20, 0 of 15, 0 of 15), whatever the app does for its owner. The security programme line doesn't need an interface and is scored. The security page publishes a responsible disclosure route (ops@natura.inc, acknowledgement within 72 hours), though the security.txt it links returns 404. It lists SOC 2 Type I as audited, GDPR and Swiss FADP compliance and Google CASA Tier 2 in review, and claims regular third-party penetration tests. No bug bounty or advisories found. A completed SOC 2 Type I and a published disclosure route sit above Hark's 8 for a security.txt and SOC 2 in progress (10 of 20).

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

Why it scored 10: Graded on the interface an outside agent can use, as GRADER.md asks. tinyNature has no API, MCP server or A2A endpoint, and its Telegram bot is a chat for people. The contract, description, typed-input and example lines score nothing (0 of 25, 0 of 20, 0 of 15, 0 of 15), which says nothing about the agent for people. natura.inc/llms.txt lists the site's product, legal and company pages with a short summary of the company (10). The versioning and changelog line versions an agent interface, and with none there is nothing to version, so it scores nothing (0 of 15). We read it this way for every listing in this batch without an agent interface, and app release notes count under maintenance instead.

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

Why it scored 30: Read with the hosted rule, on tinyNature. No x402, MPP or L402 (0). The HumanPods page states tinyNature Pro's normal price as $20 a month and sells HumanPods at $149 with the Free plan or $240 with 12 months of Pro, with no standalone plan page, so plan-only (10). A person starts tinyNature by sending a message on iMessage, WhatsApp or Telegram, with no form or card step, and the HumanPods page names a tinyNature Free plan (20). Starting needs a person's messaging account, not a programmatic route (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.

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

Why it scored 4: Read for a closed service. No dated release, changelog entry or app-store listing found. The subprocessor page was updated on 8 October 2026, which isn't a product change (0). No dated entries in the last 90 days (0). No changelog, with a Discord the site names for product updates and conversations with the team, and ops@natura.inc, neither tested (4 of 15). No MCP server or SDK (0). No package or CI to judge (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.

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

Made of editorial 58, provenance 47.

Why it scored 53: Closed service under terms of 30 May 2026 (15). The privacy policy of 24 September 2026 has a retention table (conversations, voice notes and health data for the life of the account, location as the latest point only), keeps health data out of training, and agrees with the subprocessor and security pages on Supabase in Frankfurt. It says data isn't used to train third-party models for unrelated purposes, which leaves Natura's own training unaddressed (22 of 30). Subprocessor changes get at least 30 days' notice and material term changes get notice, with no deprecation policy for the service (6 of 20). The subprocessor table names each provider with purpose, data, region and legal basis, but lists AI model providers only as a category, and they are the processors that see conversation text (15 of 20).

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: natura.inc, registered 2026-03-23 (under a year) (0 of 15)
- Status page: not found (0 of 10)
- Changelog: not found (0 of 10)
- security.txt: not found (0 of 10)

## 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 Natura trains its own models on conversations. The privacy policy addresses only third-party training.
- Which AI model providers handle conversations. The subprocessor page doesn't name them.
- The SOC 2 Type I report wasn't seen. The security page lists it as audited.
- No standalone tinyNature Pro subscription page was found.

## Weaknesses

- No API, MCP server or A2A endpoint for an outside agent.
- The security page links a security.txt that returns 404.
- No status page, changelog or dated releases found.
- AI model providers aren't named on the subprocessor page.
- The Interface ring is waitlist only, with price and timing not set.

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

- Don't plan to call tinyNature from another agent. @tinyNatureBot on Telegram is a chat for the owner, not an API.
- Send security reports to ops@natura.inc. The security.txt the site links returns 404.
- Check that tinyNature works on the owner's platform before they order HumanPods, as the HumanPods FAQ advises.

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