Support
Contact
Section titled “Contact”Email support@predictefy.com. Account, billing, and credit-balance questions all go to the same address.
Do not include an API key in a support message. If a key may have been exposed, revoke it at portal.predictefy.com/keys first — the raw value is shown once and stored only as a hash, so revoking and re-creating is the only remedy.
Before reporting a bug
Section titled “Before reporting a bug”Most reports resolve faster with four things, and three of them come back in the response you already have:
- The request — verb, exchange segment, and parameters, with the key redacted.
- The
codefrom the error envelope, not just the HTTP status.codeis more specific and is what identifies the path taken. asOfandprovenancefrom the response. These say when the data was captured and which pipeline produced it — the two things that distinguish stale data from wrong data.- Whether it reproduces. One occurrence and a consistent one need different investigations.
Things that are answers, not faults
Section titled “Things that are answers, not faults”Three responses are commonly reported as bugs and are working as designed:
NOT_SUPPORTED— the venue does not expose that capability. It is a statement about the world, not a failure. See Capability-honest data.- A synthetic order book — venues without a real book return a book-shaped response labelled synthetic. It is price, not executable depth.
- A price gap between venues — reported as an indicative price discrepancy. Venues disagreeing is normal market behaviour; see Cross-venue data.
For 429 and 503, check Rate limits & retries first — both are
retryable and both have a documented backoff.
Checking what the API says about itself
Section titled “Checking what the API says about itself”Several answers are available without asking anyone:
- The venue’s
hasmap reports its own capabilities per verb. - Venue coverage records book type, trades tape, and history per venue.
- The API reference is generated from the OpenAPI contract that gates the implementation, so it cannot drift from the served routes.
For agents
Section titled “For agents”/llms.txt is a self-contained brief written to be pasted into an AI agent, and
/llms-full.txt is the full corpus. Every guide page is also available as raw Markdown at
its own URL plus .md.