Support

Last updated: 17 October 2026.

Contact [email protected] for SourceKeel account, API, data, or billing help. Scydex Ltd operates SourceKeel at 320 City Road, London, England, EC1V 2NZ. You can browse this page without an account. Signed-in customers can use the form below. Paid plans include email support. Sandbox accounts can use the documentation and the agent guide, and can still email us about their account or billing. We answer on UK working days. We do not promise a response time.

Tickets

Each support request is a ticket: a thread of messages between you and SourceKeel. Signed-in customers can read and reply to their tickets in the console, under Support. A person signed in to the account sees every ticket on it. An agent using a key sees only the tickets that key opened. Messages from an agent are always marked as the agent's. Before we store a message, we remove anything that looks like a key, token, or password. A small number of SourceKeel staff read and answer tickets. Staff cannot see your keys or tokens, and cannot act as you. We email you when staff reply. When an agent opens a ticket, we email you its ticket number and topic, never its words, unless you turn off agent-request emails on the Activity page.

Help for people

Read the API documentation for endpoint examples, coverage, credits, and limits. For a question, include your account email and a clear description. For a data issue, include the entity or filing ID, expected result, actual result, and source link. You can also report a wrong value as a correction, in the console or through POST /v1/corrections, and follow its status there. For a billing issue, include the invoice, receipt, or purchase ID. See the refund policy for credit corrections and refund requests.

Help for agents

Agents can open and follow tickets through /v1/support/tickets with their key or API session. Agents use the same support inbox for their authorized operator. An AgentMail-style inbox can receive replies if your provider allows them. Keep that inbox available for verification, receipts, and support. We do not require an agent to disclose its full prompt or conversation history.

Read the agent guide and OpenAPI document for supported machine interfaces. Use the documented email-code sign-up, session, and key flows. Check billing before authorizing an available machine purchase. For a purchase retry, keep the original idempotency key and verify the receipt.

If an MCP client or Zapier workflow fails, identify the client and the failing tool or action. Include the underlying API result where available. Your platform's extra fees and permissions follow its own terms. The agent guide identifies supported interfaces.

Useful diagnostic details

• The route and method, with secret values removed.
• The HTTP status and error code.
• The request ID, response ID, and data version where supplied.
• The time, including timezone, and a minimal reproduction.

Respect Retry-After when the service returns a rate limit or temporary failure. Do not retry continuously while waiting for support. Never send an API key, session token, password, verification code, full card details, or wallet private key.

Other contacts

Use [email protected] for legal notices and privacy requests. To download a copy of your data or delete your account, use Account settings in the console. The privacy policy explains what each one covers. Use the security page to report vulnerabilities. On a paid plan, use the signed-in feature request page to ask for new coverage. An unavailable value or an explicit need does not promise a delivery date.

Sign in to use the support form, or email us without an account.