LlamaIndex integration
LlamaIndex API key setup with prepaid controls
LlamaIndex can create valuable AI workflows, but document ingestion, repeated retrieval calls, and long answers can make spend hard to predict. NexRelay gives developers building retrieval and document workflows a controlled gateway key before scaling usage.
How LlamaIndex fits
LlamaIndex belongs to SDK-based OpenAI-compatible applications. The safest setup is a dedicated gateway key, a compatible endpoint, and a small first budget so one client can be tested without exposing a broad provider key.
Recommended setup
Start with a small key for indexing and test retrieval prompts before scaling usage.
- Create one key for this client only
- Start with a small daily or monthly budget
- Use model allowlists for early testing
- Review request logs after the first successful call
What to verify
After the first request, check that the expected model, endpoint, token meters, billed amount, and status appear in the usage ledger. Increase limits only after the route behaves as expected.
FAQ
Can LlamaIndex use a NexRelay API key?
LlamaIndex can use NexRelay when the client supports a compatible custom base URL and API key for its request style.
Why use a separate key for LlamaIndex?
A separate key makes spend easier to cap, audit, rotate, and disable without affecting other tools.