Your first Neurico call in 5 minutes

This guide takes you from a clean account to your first GET /v1/models and POST /v1/responses calls. The goal is to connect Neurico to your existing app with the fewest possible changes.

The self-serve entry point for this flow is the private endpoint onboarding screen. Once setup is complete, you can go live the same day using the API reference and the OpenAI migration guide in the docs.

1. Create your account and verify your email

1. Open the Private endpoint screen.
2. Enter your work email and request a verification code.
3. Confirm the 6-digit code that arrives.
4. If this is your first sign-in, the system takes you to the endpoint-creation step.

At the end of this step, Neurico creates a session for you. If KVKK consent is missing, the product automatically redirects you to the compliance screen.

2. Create an endpoint

On the onboarding screen, type your endpoint name and create it. For teams with an active Starter or Growth subscription, a single production endpoint is prepared based on the tier scope.

The created endpoint produces two URL formats:

• Production primary URL: https://{slug}.gateway.neurico.ai/v1
• Local or proxy fallback URL: https://neurico.ai/api/gateway/{slug}/v1

In production the base contract is subdomain-based. For local development and staging environments you can use the path fallback.

3. Get your API key

After the endpoint is created, the dashboard returns a one-time plaintext API key. This key is in the nrc_<prefix>.<secret> format and is not shown in plain text again afterwards.

Save the key to a secure secret store and use this header in requests:

Authorization: Bearer nrc_xxxxx.yyyyy

4. List the models

For a first health check, send the GET /v1/models call first:

curl https://team-alpha.gateway.neurico.ai/v1/models \
  -H "Authorization: Bearer nrc_xxxxx.yyyyy"

Local fallback example:

curl https://neurico.ai/api/gateway/team-alpha/v1/models \
  -H "Authorization: Bearer nrc_xxxxx.yyyyy"

Expected successful response:

{
  "object": "list",
  "data": [
    {
      "id": "neurico",
      "object": "model",
      "owned_by": "neurico",
      "deployment_mode": "hosted-shared",
      "status": "ACTIVE",
      "routed_model": "gpt-5.4-mini",
      "provider_profile": "openai"
    }
  ]
}

5. Send your first response call

When the model list arrives, make a Responses API call with the same base URL:

curl https://team-alpha.gateway.neurico.ai/v1/responses \
  -H "Authorization: Bearer nrc_xxxxx.yyyyy" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "neurico",
    "input": "Summarize the record-keeping policy from a KVKK standpoint in two bullet points."
  }'

Neurico forwards the request body to the upstream in an OpenAI-compatible way and returns the response in the same format.

6. What should I check when setup is complete?

• GET /v1/models should return 200
• POST /v1/responses should return 200
• The endpoint base URL should be visible in the dashboard
• Your API key should be stored in a secret manager or similar
• If KVKK consent is missing, the compliance screen should be completed

Next steps

• API reference to see the request-response shape and error behavior
• Migration guide if you use the OpenAI Python SDK
• KVKK guide for disclosure, explicit consent and audit export operations