CONTACT
Contact us
Picking the right channel gets you an answer faster. For account and billing requests, please write from your registered email so we can confirm who you are.
Technical support
Integration errors, unexpected retrieval results, API key and quota problems, MCP clients that will not connect. Include the time of the failure and the request id.
support@re0.comClaims and content appeals
Claiming ownership of a public library, debugging a failed claim, or a source owner asking for content to be removed or corrected. Ownership is still decided by DNS TXT or well-known verification.
claims@re0.comPartnerships
Bulk integration, content partnerships, distribution and press. Tell us your team size, expected call volume and the use case.
partners@re0.comSecurity disclosure
Vulnerabilities, data exposure or abuse. Please do not disclose an unfixed issue publicly, and do not touch other users’ data or quota while testing.
security@re0.comCHECKLIST
Bring these along
Full context up front usually saves a round trip or two.
- When it failed (with time zone) and roughly how long it lasted
- The Library ID involved, for example /vercel/next.js
- The request id from the response, or your MCP client’s error output
- The first 6 characters of the API key (never the whole key)
- What you expected, and what you actually got
We will never ask for your full API key, account password or payment details, by email or any other channel. Forward anything that does straight to security@re0.com.
ELSEWHERE