Legal

API & MCP Terms

Effective date:October 24, 2026Today

Summary (Plain-English)

Rules for programmatic access to Huntertech.io through our REST API, MCP integrations, and API keys. These terms supplement the Terms of Service and apply to all API and MCP use.

By creating or using an API key, calling our REST API, or connecting an MCP client, you agree to this document and our Terms of Service. Technical limits and documentation are published at /api and /vendor-mcp.

1. Access and authentication

API keys are tied to your account and plan. Keep keys confidential; you are responsible for use under your keys.
Do not share keys in public repositories, client-side code, or untrusted third-party tools.
We may revoke keys that leak, abuse quotas, or violate these terms.
You are responsible for calls made with your keys, including calls from an AI agent, MCP client, or script you connect. Those tools act as you.

2. Acceptable use

Respect published rate limits and plan entitlements;
No scraping or bulk export beyond what your plan and endpoints allow;
No attempts to bypass authentication, quotas, or security controls;
No use that degrades the service for other customers or violates applicable law;
Use the API or MCP only against systems and accounts you are allowed to test. Do not probe, scan, or load-test a third party's systems through Huntertech.io;
Do not resell, sublicense, or operate a competing data feed from Huntertech.io responses. You may use the data inside your own operations and, with attribution to Huntertech.io and a link to the vendor's official status page, quote short factual excerpts;
Vendor incident and status data may come from third-party sources; do not republish it in ways that misrepresent Huntertech.io or the underlying vendors. See our Disclaimer.

3. MCP integrations

MCP tools expose a subset of vendor intelligence data according to your plan. Tool availability may change as we ship updates. OAuth and API-key flows must use official Huntertech.io endpoints only.

4. Changes and enforcement

We may modify endpoints, fields, limits, or these terms. Material changes are emailed to the address on your account and posted here before they take effect. If you do not agree, stop calling the API and revoke your keys before that date. Report abuse to [email protected].

1. Access and authentication

API keys are tied to your account and plan. Keep keys confidential; you are responsible for use under your keys.

Do not share keys in public repositories, client-side code, or untrusted third-party tools.

We may revoke keys that leak, abuse quotas, or violate these terms.

You are responsible for calls made with your keys, including calls from an AI agent, MCP client, or script you connect. Those tools act as you.

2. Acceptable use

Respect published rate limits and plan entitlements;

No scraping or bulk export beyond what your plan and endpoints allow;

No attempts to bypass authentication, quotas, or security controls;

No use that degrades the service for other customers or violates applicable law;

Use the API or MCP only against systems and accounts you are allowed to test. Do not probe, scan, or load-test a third party's systems through Huntertech.io;

Do not resell, sublicense, or operate a competing data feed from Huntertech.io responses. You may use the data inside your own operations and, with attribution to Huntertech.io and a link to the vendor's official status page, quote short factual excerpts;

Vendor incident and status data may come from third-party sources; do not republish it in ways that misrepresent Huntertech.io or the underlying vendors. See our Disclaimer.