BYOK AI Providers

NeuralRepo’s AI features are powered by Bring Your Own Key (BYOK). You connect your own API key from a supported provider and NeuralRepo uses it for AI-generated specs, weekly digest summaries, and other intelligent features.

What BYOK Enables

Feature	Description
AI-Generated Specs	The /ideas/:id/develop endpoint uses your key to generate a full project specification from an idea.
Weekly Digest	Your Sunday digest includes an AI-written summary of the week’s ideas, connection suggestions, and stale idea flags.
Future Features	Auto-tagging, idea enrichment, and smart grouping are on the roadmap — all powered by your key.

Without a BYOK key, these features are unavailable. Core functionality (capture, search, organize, graph) works without any AI key.

Supported Providers

Provider	Models	Key Format
Anthropic	Claude 3.5 Sonnet, Claude 4 Sonnet, Claude 4 Opus	sk-ant-...
OpenAI	GPT-4o, GPT-4o-mini	sk-...
OpenRouter	Any model available on OpenRouter	sk-or-...

Setup

Web App

1. Go to Settings > AI Providers in the NeuralRepo web dashboard.

2. Select your provider (Anthropic, OpenAI, or OpenRouter).

3. Paste your API key.

4. Click Save. The key is encrypted and stored securely.

5. Click Test Connection to verify the key works.

API

Use the BYOK API endpoints to manage keys programmatically:

# Set a provider key
curl -X PUT https://neuralrepo.com/api/v1/user/byok/anthropic \
  -H "X-API-Key: nrp_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"api_key": "sk-ant-your-anthropic-key"}'

# Test the key
curl -X POST https://neuralrepo.com/api/v1/user/byok/anthropic/test \
  -H "X-API-Key: nrp_your_key_here"

Replace anthropic with openai or openrouter for other providers.

Provider Priority

When NeuralRepo needs to make an AI call, it selects a provider in this order:

1. Your explicit preference — if you have set a preferred provider in settings, that is used first.
2. Anthropic — if an Anthropic key is configured.
3. OpenAI — if an OpenAI key is configured.
4. OpenRouter — if an OpenRouter key is configured.

If no key is available for any provider, the AI feature is skipped gracefully (for example, the weekly digest is sent without an AI summary).

Security

Your API keys are protected with multiple layers:

• Encrypted at rest. Keys are encrypted using the server-side ENCRYPTION_KEY before being written to the database. The plaintext key is never stored.
• AI Gateway routing. All AI requests are routed through Cloudflare’s AI Gateway, which provides logging, rate limiting, and caching without exposing your key to additional third parties.
• No key exposure. The API never returns your full key. GET endpoints return only the last four characters for identification.

Caution

NeuralRepo never shares your API key with anyone other than the selected AI provider (via AI Gateway). However, usage of your key by NeuralRepo counts against your provider’s billing. Monitor your provider dashboard for unexpected usage.

Managing Keys

# List configured providers (returns provider names and last 4 chars of key)
curl https://neuralrepo.com/api/v1/user/byok/status \
  -H "X-API-Key: nrp_your_key_here"

# Remove a provider key
curl -X DELETE https://neuralrepo.com/api/v1/user/byok/openai \
  -H "X-API-Key: nrp_your_key_here"

Testing Your Key

Before relying on AI features, verify your key works:

curl -X POST https://neuralrepo.com/api/v1/user/byok/anthropic/test \
  -H "X-API-Key: nrp_your_key_here"

Success response:

{
  "ok": true
}

Failure response:

{
  "ok": false,
  "error": "Invalid API key"
}