Accounting
Operations for journal entries, accounting periods, reconciliation and reports without binding the model to one country's chart of accounts or tax forms.
Open operation registry
One operation language for every system.
Describe an action once. Connect business services, CAD systems and equipment through shared contracts and reusable adapters.
The problem
Calculate delivery, create a payment or extrude a CAD profile: each action needs a clear contract. OpsRegistry separates its meaning from API field names, local identifiers and authentication details.
The registry is independent of any ERP, CAD system or agent platform. Applications can use its contracts and implement adapters; an operation definition alone does not mean a working integration is available.
Current domains
Domains cover business processes, software and engineering. Draft definitions and verified implementations are different stages: check operation status and adapter support before execution.
Operations for journal entries, accounting periods, reconciliation and reports without binding the model to one country's chart of accounts or tax forms.
Provider-neutral parametric sketches and solid modelling.
Provider-neutral commercial exchange independent of manufacturing, accounting and payment execution.
Operations for reading, creating, sending, signing and processing electronic business documents without binding applications to one EDI operator, signature provider or national document format.
Operations for accepting and managing payments, producing fiscal receipts and integrating related financial services.
Operations for receiving, issuing, reserving, transferring and adjusting physical inventory without binding the model to one ERP, WMS or warehouse layout.
Operations for authentication, authorization, policy evaluation and credential lifecycle management.
Operations for quoting, creating, collecting and tracking shipments without binding applications to a carrier API.
Operations for production steps such as cutting, forming, joining, assembly, inspection and packaging.
Operations for object storage and static website publication across compatible storage providers.
Provider-neutral operations for preparing signing environments, discovering devices and certificates, and creating or validating electronic signatures without exposing private keys, device PINs or local cryptographic sessions.
Operations for employees and contractors from employment through scheduling, time records, leave and payroll calculation.
The model
Defines what needs to happen in stable, provider-neutral terms.
logistics.shipment.quoteZod schemas describe normalized input, output and validation rules.
@opsregistry/contractsDeclares which provider supports an operation and under which conditions.
provider + operationImplements the contract directly or by calling other operations.
@opsregistry/adapter-cdekOne operation can have direct and composite implementations. A composite implementation calls other operations, which may themselves be decomposed further. The original contract and its guarantees remain the same.
A scenario is a reusable process template using the same composition mechanism. Implementations can start as adapter code; a shared declarative format is not implemented yet. Applications and Bridge own execution, permissions and state.
A real example
The application sends cities and cargo in one normalized format. The adapter resolves provider city IDs, authenticates when required and returns comparable delivery options.
Explore all operationsimport { createAdapter } from '@opsregistry/adapter-cdek';
const cdek = createAdapter({ clientId, clientSecret });
const result = await cdek.quoteShipment({
origin: { city: 'Samara' },
destination: { city: 'Moscow' },
deliveryMode: 'terminal_terminal',
packages: [
{ weightKg: 10, lengthCm: 100, widthCm: 20, heightCm: 20 },
{ weightKg: 5, lengthCm: 20, widthCm: 20, heightCm: 50 }
]
});
console.log(result.options);For AI agents
A concise project map, full context and versioned JSON snapshots are available as plain, crawlable resources.
/registry.jsonProject manifest and dataset map /data/operations.jsonOperation definitions /llms-full.txtComplete agent context /mcpReserved for the public MCP serverplannedOpen by design