Developers

For Developers

Build on the Oriva Platform

REST API, TypeScript SDK, Plugin SDK, MCP Server, and CLI — all driven by the same OpenAPI spec. What you can do in the app, you can do in code.

Get Access Token MCP Server →CLI →TypeScript SDK →

json · claude_desktop_config.json

{
  "mcpServers": {
    "oriva": {
      "command": "npx",
      "args": ["-y", "@oriva/mcp-server"],
      "env": {
        "ORIVA_API_KEY": "oriva_pk_live_..."
      }
    }
  }
}

Why now

An agent-native moment

Most platforms still ship REST and call it a day. We shipped the SDK, the CLI, and the MCP server on the same OpenAPI source — so the same operation your code calls, an agent can call too. The agent-native surface is already there; build on top of it before the rest of the ecosystem catches up.

One spec, four surfaces

Every endpoint reaches developers as REST, typed TypeScript, shell subcommand, and MCP tool — all regenerated from a single OpenAPI source.

Built where agents already work

Claude Code, Claude Desktop, Cursor, Continue — one line of config and Oriva tools appear in the picker. No bespoke connector per client.

New endpoints ship everywhere at once

A change to the spec regenerates the SDK, the CLI, and the MCP tool list together. No per-client wiring drift, no months-long client lag.

Five ways to build

REST APIGA

curl … /api/v1/entries

Full HTTP access to your Oriva data. 50+ endpoints, OpenAPI 3.1 spec, interactive reference.

API reference ↗

TypeScript SDKGA

npm install @oriva/sdk

Type-safe Node.js and browser client with typed responses, error classes, and env-var auth.

SDK docs →

Plugin SDKPrivate Beta

clone 0riva/o-platform

Build embedded marketplace apps with entry, template, UI, and storage APIs. React hooks included. Ships from source until public npm release.

Plugin docs →

MCP ServerGA

npx @oriva/mcp-server

Drop Oriva into Claude Code, Claude Desktop, Cursor, or Continue. 46 endpoints as tools any LLM can call.

MCP docs →

CLIGA

npm install -g @oriva/cli

Shell-friendly access for scripts, CI pipelines, and one-off automation. Every endpoint is a subcommand.

CLI docs →

Cross-surface reference — base URL, auth, rate limits, error envelope, endpoint catalog → Platform basics

Your first call in three steps

Get a Personal Access Token

Open Settings → Personal Access Tokens and create one. Tokens are scoped to your account, grant read+write, and start with oriva_pk_live_ (or oriva_pk_test_ for sandbox use).

Open settings →

Install the SDK

shell

npm install @oriva/sdk

Make your first call

typescript

import { createOrivaClient } from '@oriva/sdk';

const oriva = createOrivaClient({
  apiKey: process.env.ORIVA_API_KEY!,
});

const me = await oriva.getCurrentUser();
console.log(me.data?.email);

What developers build on Oriva

Tool Connectors

Bridge Oriva and external platforms. Sync tasks, projects, and data bidirectionally.

e.g., A Jira connector that syncs sprint boards with bridge groups.

Workflow Automations

Trigger actions across the Oriva ecosystem — entry creation, agreement signing, group events.

e.g., Auto-create a Slack channel when a bridge group is formed.

Embedded Apps

Ship apps inside the Oriva marketplace. Full iframe integration with auth handoff.

e.g., A time-tracking widget attached to bridge tasks.

Data Enrichment

Add intelligence to Oriva data. Analyse, tag, or transform content on the platform.

e.g., An AI service that auto-categorises marketplace listings.

Roadmap — in design

Building toward fair credit for contributions

Today you can build, ship, and earn through the marketplace. We are designing the layer underneath: a contribution-event ledger — REA-style Resources, Events, Agents accounting — so the platform can attribute and meter what every plugin, automation, and agent actually does. The intent is direct micro-payments to the people whose code produced the value, not just the storefront owner.

Contribution-event ledger

Every meaningful action — an entry served, a workflow fired, a tool called — emits a typed event with a stable resource ID.

Attribution across the stack

When your plugin triggers the action, your account is the credited Agent on that event — even if the action lands on another developer’s Resource.

Micro-payments on existing rails

When the ledger goes live, contribution events route payouts through the same Stripe Connect rails the marketplace already uses today.

Public contract

The ledger spec, the event schema, and the payout formulas are all public. You can independently verify what you are owed.

Early-builder program

The first 100 builders shape the contract, get named credit on launch, and get early access to REA payouts the moment they ship. The ledger is being designed in the open — your input on event shape, attribution rules, and payout formulas lands directly in the spec.

Ready to build?

Get your API key and start building in minutes. Join the developer program for early access to new surfaces and a direct line to the team.

Get Access Token

Contents will appear as entries load.

Collabs

Dominoes

Groups

Pulse

Oriva