YOOtraffic API and MCP server

Everything this site publishes is available to programs as well as to people: a read-only JSON API, an MCP server, and a markdown representation of every page. No key, no signup, no rate limit beyond ordinary abuse protection.

YOOtraffic Content API

A public REST API over the product catalog, the pricing model, the page index, page text, and the blog. It answers questions about the product. It does not order traffic or manage a campaign: that happens in the account application and is not exposed here.

OpenAPI 3.1 specification
https://yootraffic.com/openapi.json
Authentication
None. Every endpoint is public, read-only, and readable cross-origin.
Response format
JSON, UTF-8, cached for five minutes at the edge.

Endpoints

Generated from the OpenAPI document, so this list and the specification cannot disagree.

MethodPathoperationIdSummary
GET/api/v1getServiceIndexDescribe the API
GET/api/v1/productslistProductsList products
GET/api/v1/products/{productId}getProductGet one product
GET/api/v1/pricinggetPricingGet the pricing model
GET/api/v1/pageslistPagesList public pages
GET/api/v1/contentgetPageContentGet a page as markdown
GET/api/v1/postslistBlogPostsList blog posts
GET/api/v1/searchsearchSiteSearch pages and posts

Quick start

Three calls cover most of what an agent needs: what is sold, what it costs, and what a page says.

curl https://yootraffic.com/api/v1/products
curl https://yootraffic.com/api/v1/pricing
curl "https://yootraffic.com/api/v1/content?path=/en/pricing"

MCP server

The same operations as MCP tools over the Streamable HTTP transport. Point any MCP client at the endpoint below. There is no authorization step, and the server keeps no session because every tool is a pure read.

Endpoint
https://yootraffic.com/mcp
Transport
Streamable HTTP (POST, JSON-RPC 2.0)
Server manifest
https://yootraffic.com/mcp.json

Client configuration

{
  "mcpServers": {
    "yootraffic": {
      "type": "http",
      "url": "https://yootraffic.com/mcp"
    }
  }
}

Tools

  • list_products

    List every YOOtraffic product with its traffic type, billing unit, entry price, and what is included. Use this to answer what the company sells.

  • get_pricing

    Unit prices for every product plus the account terms (minimum deposit, refunds, balance expiry) and an explicit list of what the service does not deliver. Prices are USD, pay-as-you-go, no subscription. Call this instead of quoting a price from memory.

  • list_pages

    The index of every public page with its title, description, URL, and markdown URL. Use it to find the page that answers a question before fetching its text.

  • get_page_content

    The full text of any public page as markdown, including blog posts and legal documents. Give a site path such as /en/pricing or /en/blog/some-post.

  • list_blog_posts

    Published articles, newest first, with title, excerpt, date, and markdown URL.

  • search_site

    Search page titles, page descriptions, and article titles and excerpts. Returns URLs and markdown URLs so the matching text can be fetched directly.

Markdown for every page

Every page serves a markdown representation as well as HTML, so a crawler never has to parse the layout to read the text.

  • Send Accept: text/markdown to any page URL and the same page comes back as markdown.
  • Or append .md to the path: https://yootraffic.com/en/pricing.md
  • Responses carry Vary: Accept and a Link header pointing at the markdown sibling.
  • An Accept header that rejects both representations gets a 406 rather than a guess.
  • A path that does not exist returns a real 404 with a markdown body listing where to go instead.

Machine-readable files

Questions

Write to support@yootraffic.com. If an endpoint is missing something you need, say what you are building and we will look at adding it.