The Overview section is your operational dashboard. It shows:

• Usage metrics — total requests, errors, and a recent activity sparkline at the top of the page.
• Key Ownership card — active keys, unassigned keys, and the top owner by request volume.
• Cost Attribution card — attributed vs. unattributed spend and the highest-cost key.
• Webhook Health card — active endpoints, recent success rate, and last failure timestamp.
• Security Alerts card — keys expiring soon, open IP/origin policies, and denied audit events in the last 7 days.

Each card contains Go there links that jump directly to the relevant section.

API keys authenticate every request to the index. Manage them here:

• Create — enter a label, pick a scope (search), and submit. The raw key is shown once — copy it immediately.
• Revoke — instantly disables a key; any in-flight requests using it return 401.
• Rotate — issues a replacement key with an optional overlap window (minutes) so existing callers have time to update.
• Policy — restrict a key to specific allowed actions, set an expiry date, whitelist IP addresses or request origins.
• Owner — the Owner column shows which portal user created each key, powering the cost-attribution breakdown in Billing.

Admin users see all keys; Developer users see only the keys they created.

The Query Console lets you test search queries without writing any code.

• Select an API key from the dropdown — the list shows all keys available to your account.
• Enter a query term and an optional result limit, then click Search.
• JSON results appear in the output panel with syntax highlighting.
• Queries made here count against real usage, so they appear in your Billing and Audit logs.

The Billing section provides full cost visibility:

• Usage summary — current-period request count and total cost at the top.
• By-key breakdown — cost and request count per API key, ranked highest first.
• By-owner breakdown — aggregated spend per team member who owns keys.
• Export CSV — download a spreadsheet with key ID, owner email, request count, and cost for accounting or auditing.
• Credits & invoices — view applied credits and link to payment portal (requires Billing role).

Cost is calculated at $0.001 per request by default and shown in USD.

The Team section is available to Admin users and lets you manage who has access to the portal.

• Invite member — enter an email address and choose a role; an invitation is sent immediately.
• Change role — update a member's role at any time; the change takes effect on their next page load.
• Remove member — revokes portal access. Any API keys the member owns remain active until manually revoked.

See Roles & Permissions below for a full capability matrix.

Webhooks push real-time event notifications to your own HTTPS endpoint.

• Register endpoint — provide your HTTPS URL, a shared secret for HMAC verification, and choose which event types to subscribe to (search, key.created, key.revoked, etc.).
• Delivery log — see the HTTP status of every delivery attempt and the response body.
• Retry — manually re-trigger a failed delivery from the log table.
• HMAC verification — each delivery includes an X-Webhook-Signature header. Verify it with your secret using SHA-256 HMAC to confirm authenticity.

Webhooks require Admin or Developer role.

The SDK & Snippets section provides language-specific code examples and integration patterns.

• Key selector — pick an API key and all code snippets automatically include it.
• SDK quickstarts — copy-ready Node.js and Python SDK examples pre-filled with your key for rapid setup.
• Verify SDK — minimal verification snippets to test your environment is properly configured.
• HTTP reference — ready-to-use cURL, Python requests, and JavaScript fetch snippets for every endpoint.
• Feature parity — quick matrix showing which SDK capabilities are supported.

The Endpoint Sandbox is your interactive API explorer and testing ground.

• Quick templates — pre-configured requests for common tasks (connectivity test, RAG retrieval, billing snapshot, audit events, webhook health).
• Recent history — load a request you ran previously to reuse or modify it.
• Custom builder — manually select an endpoint, construct a query, set limit, and run live.
• Response inspection — see status code, latency, full JSON response with syntax highlighting.
• Code export — copy the exact request as cURL, Python, or JavaScript to use in your code.

Sandbox requests count as real usage, so they appear in Billing and Audit logs.

Service access is entitlement-driven and managed in the Dev Portal.

• Standard Search — available on Search API, Index API, and Enterprise.
• Bulk Search — available on Index API and Enterprise.
• Enterprise Jobs — available on Enterprise only via portal-managed export workflow.
• Higher tiers include lower-tier services — Index includes Standard Search, Enterprise includes Standard + Bulk + Jobs.

Use Query Console and API key controls in the portal to set up and validate access for your plan.

The Audit Tools section maintains an immutable event log of all portal and API activity.

• Filter by date range — narrow events to a specific window.
• Filter by status — show only success or denied events to spot access problems quickly.
• Filter by key ID or actor email — trace all actions by a specific key or team member.
• Text search — full-text search across event details (e.g. "policy", "rotate").

Audit logs are read-only and cannot be deleted. Only Admin users can view the Audit section.

Scopes

Each API key carries a set of allowed actions: search (query the index). A key without the matching scope receives a 403 Forbidden response.

Key Policy

Policies add additional restrictions on top of scopes — an expiry date, an IP allowlist, and/or an origin allowlist. A request is rejected if it violates any active policy constraint.

Key Rotation

Rotation generates a new key value for an existing key record. An optional overlap window (in minutes) keeps the old value active so existing callers can update without downtime.

Cost Attribution

Every key records which portal user created it (owner). Billing rolls up request counts and cost per owner, enabling team-level spend tracking even when multiple keys are shared.

HMAC Signatures

Webhook deliveries are signed with HMAC-SHA256 using the endpoint's secret. Compute HMAC-SHA256(secret, rawBody) and compare to the X-Webhook-Signature header to confirm the payload is genuine.

Session Tokens

Portal login issues a signed, time-limited session token stored in localStorage. Tokens are validated server-side on every authenticated request; an invalid or expired token redirects to the login screen.

The portal has three roles. The role is set at invite time and can be changed by any Admin.