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 in vendor_connections.

    Setup guide →

  • Anthropic

    Available

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

    Admin API key stored encrypted in vendor_connections.

    Setup guide →

  • OpenRouter

    Available

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

    Provisioning key stored encrypted in vendor_connections.

    Setup guide →

  • Azure OpenAI

    Beta

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

    OAuth client credentials + subscription metadata stored encrypted.

    Setup guide →

  • Google Vertex AI

    Beta

    Spend from Google Cloud BigQuery billing export filtered to Vertex AI.

    Service account JSON and billing-export table fields stored encrypted.

    Setup guide →

  • AWS Bedrock

    Beta

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

    Access key and secret stored encrypted in vendor_connections.

    Setup guide →

  • Google Gemini (API)

    Beta

    AI Studio key validates; spend requires BigQuery billing export on the paid-tier GCP project.

    API key required; optional export credentials for spend (AES-256-GCM encrypted).

    Setup guide →

  • Microsoft Copilot Studio

    Beta

    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 →

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

    Setup guide →

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

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

    Import-ready journal entries for QBO Advanced. Upload your own import layout or use Meridian defaults.

    File export; Meridian does not store QBO credentials for GL Bridge.

    Docs →

  • Generic CSV

    Available

    Balanced debit/credit journal entries for any general ledger that accepts a mapped CSV import.

    File export; no ERP credentials stored.

    Docs →

  • Sage Intacct

    Beta

    Journal entries for Sage Intacct GL import. Confirm the first import in a sandbox before production close.

    File export; no Intacct credentials stored for GL Bridge.

  • NetSuite

    Beta

    Import-ready journal entries for mid-market close. Confirm the first import in a sandbox before production.

    File export; no NetSuite credentials stored for GL Bridge.

  • Dynamics 365 Finance

    Beta

    Journal entries for Dynamics 365 Finance. Confirm the first import in a sandbox before production. Business Central follows later.

    File export; no Dynamics credentials stored for GL Bridge.

  • SAP S/4HANA

    Beta

    Journal entries for SAP Upload General Journal Entries. Confirm the first import against your template before production.

    File export; no SAP credentials stored for GL Bridge.

  • 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

Available

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.