# treg.to treg.to is an API gateway and MCP server for calling tools and data providers through one endpoint and credential. It helps agents and developers use cataloged SEO, enrichment, advertising, social, scraping, and other data tools without managing separate provider keys for every metered call. - Findings24: - Site: - Preços: Freemium - Categorias: Infraestrutura para agentes de IA, Gateways e roteamento de IA, Ferramentas MCP ## O que é treg.to? treg.to provides a single API gateway and MCP endpoint for calling more than 3,800 cataloged endpoints from 108 providers. It is designed for agents and developers that need access to SEO, enrichment, advertising, social, scraping, and related data services through one token rather than separate provider credentials. A request is sent to a catalog endpoint through `https://treg.to/call/`. treg.to injects the relevant credential server-side and relays the provider's own response. The provider's path, parameters, and response format remain in use rather than being replaced by a treg.to-specific data model. The catalog can be searched by task, and platform pages show available providers alongside measured price, speed, and success-rate information where available. treg.to compares providers but does not automatically select, route between, or fail over them. Developers can use the HTTP API, CLI, MCP endpoint, or the `llms.txt` file for agent-oriented setup. ## O que treg.to pode fazer? ### Unified API and MCP access Call cataloged provider endpoints through one base URL and token, or connect an agent through the MCP endpoint. ### Server-side credential injection treg.to inserts the applicable provider credential at the gateway, so the caller does not need to hold that shared provider secret. The upstream request and response are relayed without being modeled into a separate provider API. ### Searchable provider catalog Search by task, such as backlinks, and inspect platform listings that compare providers by price, measured speed, and measured success rate. ### Bring-your-own-key routing A team's registered provider key takes precedence over treg.to's shared key. Calls made with the team's own key are not metered by treg.to. ### Pay-per-call metering Eligible calls made on treg.to's key are charged against a prepaid balance at the provider's own rate, with the rate shown before the call and no treg.to markup. New teams receive $1.00 of free credit. ### Organization tools and custom skills Teams can register their own tools and skills, including \`SKILL.md\` files, and make them available to teammates' agents through the organization's shared shelf. The API also includes routes for connections, billing, activity, calls, and tool management. ## Casos de uso ### Automated SEO research An agent can search the catalog for keyword ideas, volume, rank data, backlinks, live SERP results, or AI-visibility signals, then call the selected provider endpoints through the same gateway. ### Lead and company enrichment A workflow can combine person or company data, work-email discovery and verification, firmographics, funding information, and buying signals. Multi-step workflows may cost more per usable lead than a raw API call because misses and filtering affect the final result. ### Advertising research and operations Teams can use cataloged tools for competitor ad discovery, ad-library research, campaign management, and measurement across services such as Google Ads and Meta-related tools, subject to the provider credentials and access requirements involved. ### Social and creator analysis Agents can discover creators and retrieve supported profile, post, trend, or platform data through cataloged social tools. The catalog includes tools for platforms such as Instagram, TikTok, YouTube, and X, with availability determined by the listed provider endpoint. ### Shared internal agent tooling A team can register provider keys, connected accounts, or project skills once and let teammates' agents call them by token. This keeps credentials at the gateway and allows the organization to manage connections and access centrally. ## Perguntas frequentes ### How does an API call work? Send an authenticated request to \`https://treg.to/call/\{endpoint\}\` with the \`X-Treg-Token\` header. treg.to makes the upstream request using the provider's path and parameters, injects the credential server-side, and relays the provider's response. ### Does treg.to automatically choose the best provider? No. Catalog and platform pages provide comparison information such as price, speed, and measured success rate, but the caller chooses the endpoint. treg.to does not automatically route between providers or provide failover. ### How are calls priced? Calls using treg.to's key are metered against a prepaid balance at the provider's own rate, without a treg.to markup. The rate is shown before calling, and the first $1.00 of credit is free. Calls using a team's own provider key, registered tools, or connected accounts are not metered by treg.to. ### What happens when the prepaid balance is empty? Metered calls stop with a clear error until the balance is topped up. Calls using the team's own keys or own tools continue to work. ### Which connection options are available? The documented access options include the HTTP API, an MCP endpoint at \`https://treg.to/mcp\`, a CLI installed through \`install.sh\`, and the \`llms.txt\` file for coding-agent setup. The site also documents sign-in through GitHub, Google, or an email code. ## Informações rápidas - **Product type**: API gateway and MCP server - **Primary users**: Developers, coding agents, and teams building data workflows - **Catalog size**: More than 3,800 endpoints across 108 providers - **Main data areas**: SEO, enrichment, advertising, social, scraping, and web data - **Authentication**: X-Treg-Token for REST API requests - **Billing model**: Prepaid, metered per eligible call at the provider's rate; $1.00 free credit to start