Service status

Before reporting an issue, check the changelog for recent incidents and the OpenAPI spec for the current contract.

The service is up if GET /api/search?q=test returns 200 with a JSON body. It is down if you get a connection error, a 5xx response, or a UPSTREAM_UNAVAILABLE error.

How to report a problem

For the following, please report to the address below. Include as much detail as you can.

Bugs and unexpected behavior

• The endpoint URL you called.
• The query string (not a secret query — a normal search query that failed).
• The response code and body you received.
• The timestamp (with timezone) of the request.

Abuse reports

If a search result returned by the service hosts content that is illegal in your jurisdiction, or that infringes your copyright, trademark, or other rights, contact us with:

• The exact URL of the offending page.
• The query that returned it.
• The legal basis for your takedown request.

Note: SCOUTS-AI does not host the underlying content. We cannot directly remove content from the open web, but we can review whether a result should continue to appear through this service.

Security disclosures

If you find a security vulnerability, please report it privately (not as a public issue). We do not currently run a paid bug bounty program.

Privacy requests

For access, deletion, objection or restriction requests, include the approximate timestamp, query text, source IP used at the time if you are comfortable sharing it, and enough context for us to search operational records.

Everything else

Press, partnership, business inquiries, complaints about these terms — same address. We may take a while to reply.

Contact address

[email protected]

This address is monitored by a human, not a bot. Replies are in English.

What we will not do

• We will not sign a paid support contract, an NDA, an MSA, or a custom SLA for a free-tier service.
• We will not provide consulting, integration help, or debugging for your codebase.
• We will not promise a specific uptime, latency, or response time target.
• We will not customize search providers on a per-user basis.

If you need any of the above, please use a commercial search API.

Response time

We aim to acknowledge critical issues (service-wide outage, security vulnerability) within 7 days. We aim to respond to other reports within 30 days. We do not commit to either of these targets. The service is best-effort.

Last updated

2026-06-05.