Skip to main content
Need help, found something wrong, or want access? Here is how to reach the team and how to give us what we need to help you fast.

​
Request an API key

Keys are issued on request today. There is no self-serve signup form yet, so to get access you contact the team directly.

Email for access

neuraledgehub@gmail.com
When you ask for a key, tell us:

Who you are

Your name or organization, and a short description of what you want to build.

What you need

Which routes you expect to call. Most product and data routes need the data:read scope; operational routes need ops:read.

Expected volume

A rough sense of request volume, so we can confirm the default rate limits fit your use case.
Keys are hashed server-side and are never returned after issue. Store your key securely when you receive it. If it is lost or exposed, contact us to rotate it.

​
Get help with the API

For bugs, unexpected responses, or questions about behavior, email the same address. Before you write, the reference and the spec answer most questions.

API reference

Endpoints, parameters, scopes, and the response envelope.

OpenAPI spec

The machine-readable contract. If it is not in the spec, it is not part of the public surface.

​
Always include the request_id

Every Conduit response carries a request_id (mirrored as the top-level requestId, and inside error on failures). It identifies the exact request and lets us trace it server-side, so it is the single most useful thing to send. 
curl -i https://data.quantoraresearch.com/v1/public/observations/latest \
  -H "x-api-key: $CONDUIT_API_KEY"
# The request_id is in the JSON body, under meta.request_id (and top-level requestId).
When you report an issue, include:
  • The request_id from the affected response.
  • The full request URL (method, path, and query parameters).
  • The HTTP status and the error.code if the call failed.
  • A short note on what you expected versus what you got.
You do not need to paste your API key, and you should not. The request_id is enough for us to find the request.

​
Response times

We aim to acknowledge access requests and support email within one business day.

​
Status

For live service health, check the unauthenticated health endpoints. GET /health reports liveness and GET /ready reports readiness; neither requires a key.

Service health

https://data.quantoraresearch.com/health