Contact Search1API
Reach the team behind Search1API
The primary support address is sys@search1api.com. It reaches the Search1API team for API, MCP, CLI, SDK, proxy, account, billing, security, and privacy questions. Existing customers can also use the Help page in the dashboard, which attaches account context automatically and avoids asking you to paste identifiers into an email.
For technical support
Include the endpoint or tool you used, an approximate timestamp with time zone, the HTTP status or exact error message, and a redacted request example. A Search1API request ID is especially useful when one was returned. Never send an API key, OAuth access token, refresh token, proxy password, payment-card number, or another secret. For MCP and CLI issues, include the client name, client version, transport, and whether you authenticated with OAuth or a user-managed API key.
For billing, privacy, and security
For a credit or billing question, include the account email, transaction date, amount, and the relevant request IDs without including payment-card details. Privacy access, correction, deletion, or restriction requests should come from the account email when possible so ownership can be verified. For a suspected credential exposure or security issue, revoke the affected token or API key immediately, then describe the impact and timeline privately by email. Do not post exploitable details in Discord, GitHub issues, or other public channels.
Community and public resources
Discord is useful for general setup questions and conversations with other builders; GitHub repositories are the right place for reproducible issues in an open-source SDK, CLI, Agent Skill, or MCP package. Service availability is published on the status page. Product documentation covers authentication, credits, error handling, API endpoints, MCP setup, the official CLI, and SDKs. These public channels are not appropriate for account records, credentials, invoices, or personal information—send those to the private support address instead.