eto.tools valid

Eto API

REST/JSON API for Etsy sellers: search and research listings, build and publish them, and read orders, finance and traffic for the shops connected to an Eto account. 141 operations, base URL https://eto.tools/api/v1/, one API key in the X-Eto-API-Key header.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T14:58:46.357Z. Cached copy · Source on eto.tools

# Eto API

> REST/JSON API for Etsy sellers: search and research listings, build and publish them, and read orders, finance and traffic for the shops connected to an Eto account. 141 operations, base URL https://eto.tools/api/v1/, one API key in the X-Eto-API-Key header.

Read llms-full.txt below if you want the whole reference in one fetch; it is about 574 KB. Otherwise follow the per-endpoint links: each one is a self-contained page with the operation ID, parameters, a runnable curl/Python/JavaScript request and the errors it can return. Every path is relative to https://eto.tools/api/v1/ and every request needs `X-Eto-API-Key: eto_your_key`, generated in the API console at https://eto.tools/dashboard/api/. The API is an Enterprise feature; keys on other plans are refused with INVALID_API_KEY.

Endpoints marked "connected store" need the Etsy shop linked to the account: call GET /api/v1/stores first and use the shop_id values it returns. Rate limits are 2 requests/second and 5,000/day; on a 429 obey the Retry-After header. Do not guess paths or field names from memory — this API is not the Etsy API, and the endpoint pages below are the current contract.

Questions about the Eto app rather than the API — "where is X", "which page changes Y" — are answered by the feature map under "Where everything is" below: 1104 features across 16 pages, each with the exact path through the interface.

## Machine-readable

- [OpenAPI 3.1 (JSON)](https://eto.tools/dev/docs/openapi.json): every operation, parameter, schema and error, ready to turn into tool definitions.
- [OpenAPI 3.1 (YAML)](https://eto.tools/dev/docs/openapi.yaml): the same document in YAML.
- [llms-full.txt](https://eto.tools/dev/docs/llms-full.txt): this entire reference as one Markdown file.
- [index.md](https://eto.tools/dev/docs/index.md): the Markdown twin of the HTML reference page — the same document as llms-full.txt.
- [MCP server](https://mcp.eto.tools/mcp): the same API as MCP tools, one per operation.

## Getting started

- [API reference (HTML)](https://eto.tools/dev/docs/): the human page. Endpoint anchors are `#ep-` plus the endpoint slug.
- [API console](https://eto.tools/dashboard/api/): generate, rotate and revoke keys; configure webhooks.
- [MCP setup guide](https://eto.tools/mcp/): connecting Claude, ChatGPT or Perplexity.

## Where everything is

- [Where everything is](https://eto.tools/dev/docs/where-everything-is.md): every page, feature and control in the Eto app, with its UI path. Read this to answer "where do I change X".
- [feature-map.json](https://eto.tools/dev/docs/feature-map.json): the same map as JSON, with `path`, `url` and `api_operation_id` on every feature.
- [Dashboard](https://eto.tools/dev/docs/where/dashboard.md): The account home page: a store header, four tabs, a live order feed, a money statement with a chart, and boards for out-of-stock listings and listing performance.
- [Analytics](https://eto.tools/dev/docs/where/analytics.md): A ten-tab reportin
…

Machine-readable: GET /v1/resolve?q=eto.tools · GET /v1/domain/eto.tools · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for eto.tools:
1. POST https://agentwebmap.com/v1/sites/eto.tools/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://eto.tools/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/eto.tools/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/eto.tools).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.