Onaro™ONARO
OverviewImplementationExtraction guides
🗝️

Portkey + Meridian

Send Portkey afterRequestHook (or validated OTEL) logs to Meridian gateway ingest, handle virtual-key registry mapping, and review schema acquisition risks.

Time: 1-2 hoursDifficulty: IntermediatePotential Savings: Attribution

Best For: Teams using Portkey as an AI gateway

Portkey + Meridian gateway ingest

Status: Beta · 2026-09-22
Egress: api.onaro.io:443 (HTTPS)

Meridian maps Portkey gateway logs to OASA at POST /v1/meridian/ingest/gateways/portkey. You operate Portkey; Meridian does not store Portkey admin credentials for this path.

Prerequisites

  • Portkey gateway or AI gateway deployment
  • Meridian ingest integration key (meridian:ingest)
  • Outbound HTTPS to api.onaro.io

Ingest endpoint

POST https://api.onaro.io/v1/meridian/ingest/gateways/portkey
Authorization: Bearer MERIDIAN_INGEST_KEY
Content-Type: application/json

Recommended integration paths

Preferred: afterRequestHook webhook

Point Portkey’s afterRequestHook (or equivalent post-request webhook) at MERIDIAN_INGEST_URL with:

Authorization: Bearer MERIDIAN_INGEST_KEY

Use the env template Portkey_Meridian.env for placeholder names only.

Alternative: OTEL push (caveats)

OpenTelemetry export may batch or reshape payloads. Field paths for virtual_key, token usage, and cost can differ from the insert-a-log shape Meridian maps today. Treat OTEL as best-effort until you validate a sample payload against docs/INGEST-3-gateway-payloads.md.

Acquisition schema risk

Portkey deployments vary in which fields appear on each log line (virtual_key, api_key_id, nested response.body.usage, etc.). Meridian mapping targets the documented insert-a-log shape at version 1.10.0. After your first live request, compare the raw JSON to the fixture inventory in docs/INGEST-3-verification.md before claiming full field coverage.

Identity

  • Declared: set metadata.agent_id, metadata.cost_center on Portkey configs where supported.
  • Registry: map virtual_key / api_key_id to agents in Gateway key registry (gateway=portkey).

Verification

  1. Send one routed request through Portkey with webhook enabled.
  2. Confirm HTTP 200 from Meridian ingest.
  3. Map unmapped key refs in Meridian settings.
  4. Review Beta blockers in docs/INGEST-3-verification.md (doc-derived fixtures; no Available badge yet).

Template

See Portkey_Meridian.env in this folder.