Docs

Documentation.

Full documentation is rolling out alongside customer onboarding. Reach out and we'll share the relevant docs directly.

Platform

One robust engine behind every product.

Reconciliation Ops, Engineering First, Reporting, and Merchants Intelligence all run on the same fast, structured core — built to scale from a pilot to full transaction volume without re-architecting.

Reconciliation Ops

Continuous matching across processors, schemes, banks and ledgers — built to scale with volume.

Engineering First

The same reconciliation engine as a structured, versioned API for your own systems.

Reporting

Financial and ops reporting generated straight from the reconciled data, always current.

Merchants Intelligence

Clean names, logos, categories and subscriptions, enriched at scale.

Built for AI coding tools

Ready for your AI coding agent, out of the box.

Whether your team implements with Claude Code, Codex, or another agent, our docs and API are structured for a fast, reliable build — and we're on hand to guide the implementation directly.

agent session

$ claude "wire up the 1layer ingest client"
 
↳ reading docs.1layer.app/reference
✓ schema parsed · 7 endpoints · 3 webhook events
✓ generated src/lib/oneLayerClient.ts
✓ generated webhook handler + retry logic
 
Ready — sandbox key required to run.

Structured for agents

Docs and endpoint schemas are written to be parsed cleanly by Claude Code, Codex, and other coding agents — not just humans.

Guided implementation

Point your agent at our reference and it can scaffold ingestion, error handling, and webhook listeners correctly on the first pass.

Direct support

Our team reviews your integration alongside your AI tooling, so the first version ships fast and reliably.

MCP

An MCP server for looking into your data — not a second API.

Alongside the REST API, we run an MCP server so an agent can look up differences, tickets, and resolutions conversationally. It's a companion for ad hoc questions, not where you build your integration.

REST API

For your integration

Deterministic calls your code controls

Scheduled jobs, webhooks, cron-driven pulls

Powers dashboards, bots, and automation at volume

Runs unattended, no LLM in the loop

MCP server

For looking things up

Ask an agent about open differences or a ticket

Trigger a one-off action mid-conversation

Useful for analysts, support, and exploring during dev

Not for scheduled jobs or high-volume automation

MCP calls the same API underneath — it isn't a separate backend or a replacement for it. Build your daily-ops integration on the API; use MCP to look into the data conversationally.

Reference

Where to start.

Core references for evaluating and integrating 1Layer.

Getting Started

Send exported files or connect via API — no integration required to evaluate.

File Formats

MT940, SEPA XML, SWIFT MT103/MT202, Visa VSSS, Mastercard fee files, Amex GNS, ACH, and custom CSV/Excel.

API Reference

REST endpoints for ingestion, investigations, and reporting.

Webhooks

Subscribe to settlement, fee, and investigation events in real time.

MCP Server

Look into differences, tickets, and resolutions conversationally — a companion to the API, not a replacement for it.

Security

How we handle data confidentiality, retention, and access control.

Integrations

Connect processors, acquirers, and banks via SFTP, email, or API.

Need something specific?

Feel free to reach out to us at hello@1layer.app for the docs relevant to your integration.