Migrating from the OpenAI SDK to Neurico

Neurico's OpenAI-compatible API contract is preserved. For most teams, the only things that change are the base_url and the bearer key.

What doesn't change?

• The OpenAI client object
• client.models.list()
• client.responses.create(...)
• The shape of the Responses input
• Your downstream response-parsing logic

What changes?

• api_key becomes Neurico's key in the nrc_<prefix>.<secret> format
• base_url is updated to your endpoint's .../v1 address
• KVKK and audit operations are managed together with the dashboard

OpenAI example

from openai import OpenAI

client = OpenAI(
    api_key="OPENAI_API_KEY",
)

response = client.responses.create(
    model="gpt-4.1-mini",
    input="Summarize the rollout plan in two bullets.",
)

print(response.output_text)

Updated for Neurico

from openai import OpenAI

client = OpenAI(
    api_key="nrc_xxxxx.yyyyy",
    base_url="https://team-alpha.gateway.neurico.ai/v1",
)

models = client.models.list()
print(models.data[0].id)

response = client.responses.create(
    model="neurico",
    input="Why is audit export necessary from a KVKK standpoint?",
)

print(response.output_text)

What if I want to work with the local fallback?

If DNS or the subdomain isn't ready yet, you can continue with this base_url:

client = OpenAI(
    api_key="nrc_xxxxx.yyyyy",
    base_url="https://neurico.ai/api/gateway/team-alpha/v1",
)

Migration checklist

1. Get your endpoint base URL from the dashboard
2. Write your new Neurico API key to your secret manager
3. Update your base_url to end with .../v1
4. Verify the connection with client.models.list()
5. Run an example responses.create() call
6. If your team needs a compliance review, check the audit export flows via the KVKK guide

Common mistakes

• Forgetting to add /v1 to the end of base_url
• Not replacing the OpenAI key with the Neurico key
• Hitting the root domain without a slug instead of the path fallback
• Expecting dashboard access before KVKK consent is complete

Next steps

• API reference for request-response details
• Quickstart to set up your first endpoint from scratch