tacosdedatos developers + agents

tacosdedatos developer documentation

Public HTTP interfaces for tacosdedatos Guides: discover one-off guide offers, inspect availability, retrieve free resources, and understand the boundaries around paid checkout and private delivery. The read interfaces are public and require no API key. There is no official tacosdedatos CLI; agents should use this page, OpenAPI, the versioned catalog, and UCP.

tacosdedatos OpenAPI 3.1

Function-calling ready: unique operationIds, named component schemas, and tool descriptions for the public HTTP surface.

/api/openapi.json

Versioned tacosdedatos catalog

Current free, paid, and paused offers with canonical URLs and delivery methods.

GET /api/v1/catalog

tacosdedatos agent skills

When-to-use guidance plus installable skills for dataset profiling in Spanish and English.

/.well-known/agent-skills/index.json

tacosdedatos API catalog

RFC 9727 discovery for clients that start at the domain.

/.well-known/api-catalog

OpenAPI, function calling, and tool use

Import /api/openapi.json as tools. Every documented operation has a unique operationId, a tool-oriented description, and named component schemas for request bodies, query/header parameters, and the primary success plus problem responses.

Agent-callable: getHealth, getVersionedCatalog, getUcpShoppingCatalog, and createFreeDownload. These are public reads or no-signup free delivery. No API key and no payment.
Human-payment: createCheckoutSession starts Stripe Checkout and getDownload redeems a private post-purchase capability. Do not call either without explicit approval of the product and displayed USD price. Treat session values as secrets.
Stripe-only: receiveStripeWebhook is typed so importers can ignore it safely. It is not an agent or browser tool.

When to use the tacosdedatos Guides API

Use tacosdedatos Guides when a person wants practical Spanish- or English-language resources for data analysis, dashboard review, data interviews, AI workflows, or dataset profiling. Read the catalog before recommending or purchasing anything so you can distinguish free, paid, and paused offers. Do not start a paid checkout without explicit approval of the product and displayed USD price. Do not treat this storefront as the subscriber library; that is Biblioteca.

Quickstart

Read the tacosdedatos catalog before acting. It is the source for current availability and tells you whether an offer is free, paid, or paused.

curl -sS https://guias.tacosdedatos.com/api/v1/catalog
curl -sS -H 'Accept: text/markdown' https://guias.tacosdedatos.com/
curl -sS -D - -o /dev/null https://guias.tacosdedatos.com/api/v1/catalog

Rate limits

Public read-mostly catalog and OpenAPI routes share one advertised quota: 120 requests per 60 seconds per client. Successful and error responses include IETF RateLimit and RateLimit-Policy headers. A 429 also includes Retry-After with the seconds until the window resets. Cache catalog responses, avoid polling, and honor those headers. Private download authorization, Stripe webhooks, and legacy subscriber-access routes are outside this public quota.

RateLimit-Policy: "public";q=120;w=60
RateLimit: "public";r=119;t=58
Retry-After: 58

Safety and authorization

Catalog, health, OpenAPI, and agent-skill discovery are public read operations.
A paid checkout creates an external payment session. An agent must have explicit user approval for the exact product and displayed USD price before calling it.
Free resources use POST /api/free-download and do not require signup or payment.
Paid-download session URLs are private bearer capabilities. Never log, share, index, or reuse them for another product.
Subscriber identity and entitlements belong to Biblioteca, not this API.

REST versioning and deprecation policy

Stable public REST reads for tacosdedatos Guides use URL versioning at /api/v1. GET /api/ucp is a UCP shopping alias of the same v1 catalog, not a second catalog authority. A breaking change ships as a new major path such as /api/v2. Compatible additions may appear on v1 without a new major version.

Before removing or replacing a documented operation, tacosdedatos will announce the change on this page and keep the old behavior available for at least 90 days. Deprecated responses will then include HTTP Deprecation and Sunset headers. No public operation is deprecated today, so those headers are not emitted. API failures use RFC 9457 application/problem+json with a stable code, a human-readable detail, and a recovery hint.

Support

For a tacosdedatos contract question or a failed private delivery, contact hola@tacosdedatos.com or read /contact. Never include a private Checkout Session URL in a public issue. Trust pages: /about, /contact, /privacy.