Onaro™ONARO

Meridian by Onaro

Integrations hub

Onaro Meridian is FinOps for agentic AI: the system of record that attributes, controls and books what AI agents spend. These integrations meter spend from your stack, post audit-ready journal entries to the GL, report spend in the monitoring tools you already operate, and find unmanaged AI before it reaches 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

    AvailableAPI

    Scheduled daily spend pull from the OpenAI Costs API, by line item. Project splitting is available on request. Contact support@onaro.io. We enable it with you and confirm your first month's split together. Project splitting does not divide Scale Tier bundle cost, which remains organization-level No project spend. For per-agent attribution, send traffic through a connected gateway or OASA events.

    API key stored encrypted at rest.

    Setup guide →Attribution →

  • Anthropic

    AvailableAPI

    Scheduled daily spend pull from the Anthropic Admin Cost Report, by model. Workspace splitting is available on request. Contact support@onaro.io. We enable it with you and confirm your first month's split together. For per-agent attribution, send traffic through a connected gateway or OASA events.

    Admin API key stored encrypted at rest.

    Setup guide →Attribution →

  • OpenRouter

    AvailableAPI

    Credits-level spend sync from OpenRouter (day and model, keys combined). Manual Sync now works; scheduled sync is off by default until Onaro enables it for your org.

    Provisioning key stored encrypted at rest.

    Setup guide →Attribution →

  • Azure OpenAI

    AvailableAPI

    Spend from Azure Cost Management for Azure OpenAI deployments (tokens not included). The pull is a daily total until support turns tag splitting on. Then it groups by resource and the first cost-center tag. A rejected grouping leaves the switch off.

    OAuth client credentials + subscription metadata stored encrypted.

    Setup guide →Attribution →

  • Google Vertex AI

    AvailableAPI

    Spend from Google Cloud BigQuery billing export filtered to Vertex AI. Prerequisite: BigQuery billing export on the GCP project. Day and SKU until support turns project splitting on. Then rows also split by project id. Request labels are not read. The Vertex switch is separate from Gemini.

    Service account JSON and billing-export settings stored encrypted.

    Setup guide →Attribution →

  • AWS Bedrock

    AvailableAPI

    A daily Amazon Bedrock total from AWS Cost Explorer until support turns tags on (tokens not included). After that, the pull keeps each usage type and the first cost-center tag, including an empty tag group. For attribution before that, upload the AWS FOCUS-format Cost and Usage export instead: Meridian reads cost-allocation tags from application inference profiles, and when a cost center tag matches a department in Meridian, that department becomes the cost center on each charge whether or not an agent tag matches. An Agent tag that matches an agent name also sets the agent. Untagged usage lands in the attribution inbox with the reason shown. Prior-period corrections keep their original period and become adjustment lines once that month is locked. While the connector is active, Bedrock rows in a FOCUS upload are held for reconciliation.

    Access key and secret stored encrypted at rest.

    Setup guide →Attribution →

  • Google Gemini (API)

    AvailableAPI

    An AI Studio key validates the connection. Without a BigQuery billing export, Meridian writes no spend. Spend metering uses that export on the paid-tier GCP project (free-tier has no spend to meter). Project splitting is a separate switch from Vertex and stays off until support turns it on. Request labels are not read.

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

    Setup guide →Attribution →

  • Microsoft Copilot Studio

    AvailableAPI

    Credit-level agent attribution for Copilot Studio, valued at your rates. When Azure OpenAI is also connected, Meridian flags the overlap for review so the same spend isn't counted twice.

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

    Setup guide →Attribution →

  • Together AI

    AvailableManual upload

    Upload invoices or usage exports for Together AI, choosing Together AI at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

    Session-authenticated upload; no Together API credentials stored.

    Upload Invoice →Attribution →

  • Groq

    AvailableManual upload

    Upload invoices or usage exports for Groq, choosing Groq at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

    Session-authenticated upload; no Groq API credentials stored.

    Upload Invoice →Attribution →

  • Perplexity

    AvailableManual upload

    Upload invoices or usage exports for Perplexity, choosing Perplexity at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

    Session-authenticated upload; no Perplexity API credentials stored.

    Upload Invoice →Attribution →

  • Mistral AI

    AvailableManual upload

    Upload invoices or usage exports for Mistral AI, choosing Mistral AI at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

    Session-authenticated upload; no Mistral API credentials stored.

    Upload Invoice →Attribution →

  • Cohere

    AvailableManual upload

    Upload invoices or usage exports for Cohere, choosing Cohere at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

    Session-authenticated upload; no Cohere API credentials stored.

    Upload Invoice →Attribution →

  • AI21

    AvailableManual upload

    Upload invoices or usage exports for AI21, choosing AI21 at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

    Session-authenticated upload; no AI21 API credentials stored.

    Upload Invoice →Attribution →

  • Replicate

    AvailableManual upload

    Upload invoices or usage exports for Replicate, choosing Replicate at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

    Session-authenticated upload; no Replicate API credentials stored.

    Upload Invoice →Attribution →

  • Hugging Face

    AvailableManual upload

    Upload invoices or usage exports for Hugging Face, choosing Hugging Face at upload. Use Other vendor for an invoice that is not a listed vendor. If you reach this provider through OpenRouter, Azure, Bedrock, Vertex or a connected gateway, its spend arrives through that connection instead.

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

    Upload Invoice →Attribution →

  • Bill & invoice import

    AvailableManual upload

    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 →Attribution →

  • FOCUS CSV import

    Early accessManual upload

    Ingests FOCUS-formatted Cost and Usage datasets (v1.2+) from conforming providers in Meridian Uploads. Default tag keys are the OASA keys plus the older aliases, and they are edited on Source identities. Available to customers now. We confirm the first import with you in a sandbox before production.

    Session-authenticated file upload; no provider credentials stored.

    When does this become Available?

    After one customer completes a confirmed production import.

    FOCUS overview →Attribution →

  • Seat and license CSV

    Early accessManual upload

    Upload seat and license costs, such as Microsoft 365 Copilot or ChatGPT Enterprise seats, as a CSV. Seats are attributed to departments, not agents. Available to customers now. We confirm the first import with you in a sandbox before production.

    Session-authenticated upload to POST /api/meridian/uploads/seat-csv; no vendor credentials stored.

    When does this become Available?

    After one customer completes a confirmed production import.

    Upload Invoice →Attribution →

  • OASA event ingest

    Early accessAPI

    POST /v1/meridian/events for any system that emits OASA usage records, with a Meridian ingest key (meridian:ingest). Records with an agent_id are attributed to that agent. Available to customers now. We confirm the first import with you in a sandbox before production.

    Meridian ingest key with meridian:ingest scope; Meridian stores no vendor console credentials.

    When does this become Available?

    After one customer completes a confirmed production import.

    Attribution →

  • OpenTelemetry Collector

    Early accessAPI

    Docs-only setup: add the open-source OASA exporter to your OpenTelemetry Collector and it sends one usage record per GenAI span to Meridian, from any agent instrumented with the OpenTelemetry GenAI conventions. No in-app Connect wizard. Available to customers now. We confirm the first import with you in a sandbox before production.

    Meridian ingest key (meridian:ingest); collector and model provider credentials stay in your environment.

    When does this become Available?

    After one customer sends production usage to Meridian through the exporter's http sink.

    Setup guide →Attribution →

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

    Early accessAPI

    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. Available to customers now. We confirm the first import with you in a sandbox before production.

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

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →Attribution →

  • Kong AI Gateway ingest

    Early accessAPI

    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. Available to customers now. We confirm the first import with you in a sandbox before production.

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

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →Attribution →

  • Portkey gateway ingest

    Early accessAPI

    Docs-only setup: create a meridian:ingest key in Meridian, then POST Portkey logs to api.onaro.io. No in-app Connect wizard. Available to customers now. We confirm the first import with you in a sandbox before production.

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

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →Attribution →

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

    Early accessAPI

    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. Available to customers now. We confirm the first import with you in a sandbox before production.

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

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →

  • OpenTelemetry DCGM capacity ingest

    Early accessAPI

    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. Available to customers now. We confirm the first import with you in a sandbox before production.

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

    When does this become Available?

    After one customer completes a confirmed production import.

    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

    AvailableAPI

    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

    AvailableFile export

    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

    Early accessFile export

    File export only — journal entry zip for Sage Intacct GL import. Not a live API connector. Available to customers now. We confirm the first import with you in a sandbox before production.

    File export; no Intacct credentials stored.

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →

  • NetSuite

    Early accessFile export

    File export only — import-ready journal entry zip for mid-market close. Not a live API connector. Available to customers now. We confirm the first import with you in a sandbox before production.

    File export; no NetSuite credentials stored.

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →

  • Dynamics 365 Finance

    Early accessFile export

    File export only — journal entry zip for Dynamics 365 Finance. Not a live API connector. Available to customers now. We confirm the first import with you in a sandbox before production.

    File export; no Dynamics credentials stored.

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →

  • Dynamics 365 Business Central

    Early accessAPI

    Posts the journal for a locked chargeback run to a Business Central general journal batch, with the department as a dimension value. Available to customers now. We confirm the first import with you in a sandbox before production.

    Onaro's Entra app with admin consent; the MERIDIAN POSTING permission set limits it to one journal batch. No credentials stored per customer.

    When does this become Available?

    After one customer completes a confirmed production import.

    Setup guide →

  • SAP S/4HANA

    Early accessFile export

    File export only — journal entry zip for SAP Upload General Journal Entries. Not a live API connector. Available to customers now. We confirm the first import with you in a sandbox before production.

    File export; no SAP credentials stored.

    When does this become Available?

    After one customer completes a confirmed production import.

    Docs →

  • Workday

    PlannedFile export

    Workday 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.

    When does this become Early access?

    When it is deployed to production and usable without a feature flag.

ERPs without a direct connector 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

Early access

Pull agent spend, token rates, budget burn, anomalies, and attribution coverage into LogicMonitor with one read-only request per poll. Available to customers now. We confirm the first import with you in a sandbox before production.

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 (the share of metered agent event spend with an agent identified) 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

Early access

Vendor-neutral read API for agent spend, usage, budget, anomaly, and attribution metrics. Available to customers now. We confirm the first import with you in a sandbox before production.

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

    PlannedAPI

    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.

    When does this become Early access?

    When it is deployed to production and usable without a feature flag.

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.