Onaro™ONARO

Meridian by Onaro

Integrations hub

Meridian is the hub for AI labor cost: meter spend from your stack, post audit-ready journal entries to the GL, watch burn in the tools you already operate, and discover unmanaged AI before it hits the books.

SOURCES

Where spend comes from

Named agentic-system connectors, bill import, FOCUS file import, and OASA event ingest. Any system emitting OASA attributes can feed Meridian without a bespoke connector.

  • OpenAI

    Available

    Scheduled spend and usage pull from the OpenAI Usage API into Meridian spend records.

    API key stored encrypted at rest.

    Setup guide →

  • Anthropic

    Available

    Scheduled spend and usage pull from Anthropic Admin Cost/Usage APIs.

    Admin API key stored encrypted at rest.

    Setup guide →

  • OpenRouter

    Available

    Credits-level spend sync from OpenRouter. No per-model or token breakdown.

    Provisioning key stored encrypted at rest.

    Setup guide →

  • Azure OpenAI

    Available

    Spend from Azure Cost Management for Azure OpenAI deployments (tokens not included).

    OAuth client credentials + subscription metadata stored encrypted.

    Setup guide →

  • Google Vertex AI

    Available

    Spend from Google Cloud BigQuery billing export filtered to Vertex AI. Prerequisite: BigQuery billing export on the GCP project.

    Service account JSON and billing-export settings stored encrypted.

    Setup guide →

  • AWS Bedrock

    Available

    Spend from AWS Cost Explorer for Amazon Bedrock (tokens not included).

    Access key and secret stored encrypted at rest.

    Setup guide →

  • Google Gemini (API)

    Available

    AI Studio key validates the connection. Prerequisite: BigQuery billing export on the paid-tier GCP project for spend metering (free-tier has no spend to meter).

    API key required; optional export credentials for spend, stored encrypted.

    Setup guide →

  • Microsoft Copilot Studio

    Available

    Credit-level agent attribution for Copilot Studio — valued at your rates, reconciled to your Azure invoice.

    Entra ID app registration with read-only Power Platform licensing scopes; credentials encrypted server-side.

    Setup guide →

  • Together AI

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no Together API credentials stored.

    Upload Invoice →

  • Groq

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no Groq API credentials stored.

    Upload Invoice →

  • Perplexity

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no Perplexity API credentials stored.

    Upload Invoice →

  • Mistral

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no Mistral API credentials stored.

    Upload Invoice →

  • Cohere

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no Cohere API credentials stored.

    Upload Invoice →

  • AI21

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no AI21 API credentials stored.

    Upload Invoice →

  • Replicate

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no Replicate API credentials stored.

    Upload Invoice →

  • Hugging Face

    Manual uploadmanual upload

    Upload invoices or usage exports. Spend is captured automatically if you use this provider through Azure, Bedrock, Vertex, or a connected gateway (LiteLLM, Portkey, OpenRouter).

    Session-authenticated upload; no Hugging Face API credentials stored.

    Upload Invoice →

  • Bill & invoice import

    Availablemanual import

    Upload PDF, CSV, or Excel invoices, or enter a bill manually. Formats processed into spend records.

    Session-authenticated upload; files encrypted at rest in object storage.

    Upload Invoice →

  • FOCUS CSV import

    In development

    Being built to ingest FOCUS-formatted Cost and Usage datasets (v1.2+) from conforming providers.

    File upload path; public availability follows the FOCUS import gate.

    FOCUS overview →

  • OASA event ingest

    In development

    POST /api/v1/ingest/events for systems that emit OASA attributes. discovery.ai_usage is the enabled type today.

    Integration key with events:write scope; Meridian stores no vendor console credentials.

FOCUS is a trademark of the Joint Development Foundation. Onaro is not affiliated with or endorsed by the FinOps Foundation or the FOCUS project. Description adapted from the FOCUS Specification by FinOps Foundation, licensed under CC BY 4.0; changes were made.

GATEWAYS

Where traffic is metered

Customer-operated AI gateways (LiteLLM, Kong AI Gateway, Portkey). Meridian maps native gateway logs to OASA — you run the proxy; Onaro ingests and attributes.

  • LiteLLM gateway ingest

    Beta

    Docs-only setup: create a meridian:ingest key in Meridian, then point your LiteLLM generic_api callback at api.onaro.io. No in-app Connect wizard for the proxy.

    Meridian ingest key (meridian:ingest); LiteLLM credentials stay in your environment.

    Docs →

  • Kong AI Gateway ingest

    Beta

    Docs-only setup: create a meridian:ingest key in Meridian, then forward Kong AI audit http-log payloads to api.onaro.io. No in-app Connect wizard.

    Meridian ingest key (meridian:ingest); Kong admin credentials are not stored by Meridian.

    Docs →

  • Portkey gateway ingest

    Beta

    Docs-only setup: create a meridian:ingest key in Meridian, then POST Portkey logs to api.onaro.io. No in-app Connect wizard.

    Meridian ingest key (meridian:ingest); Portkey credentials remain in your deployment.

    Docs →

CAPACITY

Where GPU time is metered

Customer-operated DCGM exporters, Prometheus, or OpenTelemetry Collectors forward GPU utilization and power telemetry to Meridian — you run the scrape path; Onaro aggregates hourly capacity records and maps pods via the infrastructure endpoint registry.

  • Prometheus DCGM capacity ingest

    Beta

    Docs-only setup: create a meridian:ingest key, then forward DCGM-style metrics via Prometheus batches to api.onaro.io. No in-app Connect wizard.

    Meridian ingest key (meridian:ingest); Prometheus and DCGM credentials stay in your cluster.

    Docs →

  • OpenTelemetry DCGM capacity ingest

    Beta

    Docs-only setup: create a meridian:ingest key, then export OTLP JSON metrics from your collector to Meridian capacity ingest. No in-app Connect wizard.

    Meridian ingest key (meridian:ingest); collector and exporter credentials remain in your environment.

    Docs →

DESTINATIONS

Where it lands

Meridian GL Bridge produces audit-ready journal entries your controller can import — chargeback, accrual, and tie-out artifacts that match your close stack.

  • QuickBooks Online

    Available

    Manual live posting to QuickBooks Online after you lock a chargeback period (allocation id = locked run). CSV import files remain available. Scheduled draft/approval posting is not enabled yet.

    Direct posting uses Intuit OAuth; Meridian stores encrypted connection tokens and never edits existing transactions. Posts require a locked chargeback run (sandbox test exempt).

    Setup guide →

  • Generic CSV

    Available

    File export only — balanced debit/credit journal entry CSV for any GL that accepts a mapped import. Not a live API connector.

    File export; no ERP credentials stored.

    Docs →

  • Sage Intacct

    Beta

    File export only — journal entry zip for Sage Intacct GL import. Not a live API connector. Confirm the first import in a sandbox before production close.

    File export; no Intacct credentials stored.

    Docs →

  • NetSuite

    Beta

    File export only — import-ready journal entry zip for mid-market close. Not a live API connector. Confirm the first import in a sandbox before production.

    File export; no NetSuite credentials stored.

    Docs →

  • Dynamics 365 Finance

    Beta

    File export only — journal entry zip for Dynamics 365 Finance. Not a live API connector. Confirm the first import in a sandbox before production.

    File export; no Dynamics credentials stored.

    Docs →

  • SAP S/4HANA

    Beta

    File export only — journal entry zip for SAP Upload General Journal Entries. Not a live API connector. Confirm the first import against your template before production.

    File export; no SAP credentials stored.

    Docs →

  • Workday

    Planned

    Enterprise financials through mapped CSV and a read-only Meridian export your integration team can pull on their schedule.

    Planned file/API export path; wizard-only today.

Enterprise ERPs integrate through your middleware: standard-template journal files plus a read-only Meridian export — your integration team owns the pipe. Meridian conforms to YOUR files — both directions.

Zero-Access Assessment pack: Data extraction guides (web) · assessment PDFs at /guides/extraction/ — Sage Intacct · NetSuite · QuickBooks Online · Dynamics 365 Finance · SAP S/4HANA · Generic CSV / Excel · Microsoft Copilot Studio / Power Platform.

OBSERVABILITY

Where it's watched

Pull agent metrics into the platforms you already operate. Meridian stores no credentials to those platforms.

LogicMonitor

Beta

Pull agent spend, token rates, budget burn, anomalies, and attribution coverage into LogicMonitor with one read-only request per poll.

Meridian stores no LogicMonitor credentials; LM pulls with a Meridian metrics:read key.

Operational alerts

Anomaly thresholds 0.70, 0.85, and 0.95 map approximately to 2σ, 3σ, and 4σ. Attribution coverage warns below 95% — investigate gaps in Shadow AI.

Cold start and nulls

New agents emit no anomaly score until seven days of history exist. Agents without a human-entered budget emit no budget burn value, so No Data never masquerades as zero.

Read the LogicMonitor setup guide →

ANY MONITORING PLATFORM

Metrics Export API

Vendor-neutral read API for agent spend, usage, budget, anomaly, and attribution metrics.

Discover agents at /api/v1/metrics/agents and pull current spend, usage, budget, anomaly, and attribution metrics at /api/v1/metrics/current.

Build against the docs — the schema is versioned.

Any monitoring platform can subscribe via the Metrics Export API.

Read the Metrics Export API docs →Download OpenAPI →

DISCOVERY

Where unmanaged AI is found

Shadow AI discovery via event ingest closes the loop from endpoint census to ledger — without requiring a named discovery vendor on this page.

  • Shadow AI discovery

    In development

    Endpoint-census events via OASA ingest surface unmanaged AI usage in the ledger loop — discover, attribute, and promote to owned agents.

    events:write integration key; no discovery-vendor console credentials stored.

Waitlist

Tell us which systems you close in and which export sources you need. Build order follows demand.

Which systems or export sources matter to you? *

Integration availability and scope may change. Export formats are verified against current vendor documentation; customers should validate first imports in a sandbox.