The rewards & progression API

Your product. Powered by rewards.

Orishare is the rewards and progression API. Send events from your product, and your rules turn them into points, tiers, challenges and rewards, without you building the backend.

Get started for free Read the quickstart

Free for your first 10,000 actions every month. Test environments are always free.

REST APIMCP serverWebhooksAI assistant

One engine

Same infrastructure, three products.

A game, a learning app and a store send different events. The same rules engine turns each one into progress your customers can see.

See how it works

event → your rule → outcome

Game
Your game · illustrativerule: 5/5 → +150 XPquest.completed
Learning app
Your app · illustrativerule: daily lesson → +20 ptslesson.completed
Store
Your store · illustrativerule: order → tier progressorder.fulfilled

Built to work with AI, on your terms

Describe it. Orishare drafts it.

Tell Orishare the campaign you want in plain language and it drafts the rules. You review, simulate and publish, and at runtime your rules decide every reward, never a model.

See how drafting works

Your AI assistant can run it for you.

Connect the assistant your team already uses, and it can set up, integrate and run your whole program for you. In live environments you decide what it may do alone, and the rest waits for your approval.

Connect your AI Copy the prompt Agent guide

§ 01 · How it works

From an event to a moment worth having.

Four steps on one ticket. Two of them happen in your product; the two in the middle are ours to run, version and keep consistent.

01Admit one event
In your product
Your product sends an event
A player clears a quest. Your server makes one REST call. No client SDK required.
One REST call01 / 04
02Rules
In Orishare
Orishare applies your rules
The published version of your rules decides what the event is worth. Nothing is improvised.
Your published version02 / 04
03Ledger
In Orishare
Points, progress and rewards update
Balances, challenge progress and tier changes are recorded, then pushed to you by webhook.
Recorded, then pushed03 / 04
04Your screen
In your product
Your product shows the result
You read the new balance and tier over the API and draw it with your own design system.
Rendered by your code04 / 04

For exampleA game challengequest.completedAn onboarding milestonemilestone.reachedA finished episodeepisode.finishedIllustrative

§ 02 · What you get

Everything progress needs. Minus the backend.

Six outcomes your players and customers can feel. The ledgers, rule engine and controls behind them are ours to run.

01
Points that add up
Award points from any event. Balances stay consistent, and your backend reads them over the API.
02
Tiers worth climbing
Define Bronze to Gold with the thresholds you choose. Customers see exactly how far they have to go.
03
Challenges with a finish line
Multi-step goals with progress tracked for you: five dungeons, three lessons this week, one invited teammate.
04
Rewards people can redeem
Set up rewards, check eligibility and record redemptions. How a reward looks is up to your product.
05
Campaigns with guardrails
Point a campaign at an audience, give it a schedule, and cap what it can give out.
Campaign controls
- Audience. Decide which customers a campaign applies to.
- Schedule. Start and end dates, set ahead of time.
- Budget. A ceiling on what the campaign can award.
- Limits. Per-customer caps so nobody farms a promotion.
Campaign · Streak weekDraftOrishare dashboard
AudienceCustomers with 3+ lessons in the last 30 days
ScheduleMon 09:00 → Sun 23:59
Budget50,000 points total0 spent · not started
Limits1 bonus per customer, per weekapplies in test + live
SimulatePublish
06
Rules you can test first
Every change is a new rule version. Simulate it in a test environment, then publish it live.
v12 Livev13 Draft · simulated in testPOST /v1/rules/rule_…/simulateIllustrative

Also in the boxTest & live environmentsWebhooksREST APIOpenAPI specMCP server for AIBuilt-in AI assistant

§ 03 · Same engine, different products

Different screens.Same four moves.

Event, rule, update, display. Whatever your product is, the integration has the same shape.

SaaS & subscription apps

Make onboarding worth finishing.

Reward setup milestones and steady use, and run customer incentives with budgets and limits.

milestone.reached+50 pts · 3 of 4 done

Media & learning

Keep the streak going.

Finished episodes and lessons build streaks, points and weekly goals.

episode.finishedstreak 5

Commerce

Tiers shoppers chase.

order.fulfilled

Games

Quests with real stakes.

quest.completed+150 XP

Solo dev or small studio, the same API applies.

See the indie spotlight

Illustrative

§ 04 · For developers

Readable API.No surprises.

Send events over REST, read balances and progress back, and get a webhook when something changes. Every endpoint is described in the OpenAPI spec.

Test & liveBuild and simulate in test, go live when it works.
WebhooksHear about tier changes and rewards as they happen.
MCP serverClaude, ChatGPT or Cursor can set up and run everything, with your approval.

Event receipttestIllustrative

Request

POST /v1/events
Authorization: Bearer $ORISHARE_SECRET_KEY

{
  "name": "level.completed",
  "customer_id": "player_8812",
  "mode": "sync",
  "properties": { "level": 12 }
}

Response200 OK

{
  "id": "evt_…",
  "status": "evaluated",
  "execution_id": "exec_…",
  "effects": [
    {
      "type": "points.awarded",
      "currency": "points",
      "amount": 50
    }
  ],
  "trace": { … }
}

MCP server

https://api.orishare.com/mcp/connect

Then ask your AI

> Give players 50 coins when
  they win a match

Illustrative. See the API reference for exact fields.

§ 05 · Build with your AI assistant

Build with yourAI assistant.

Copy one prompt, paste it into the coding assistant you already use, then review the changes it proposes. The prompt points at the quickstart and keeps your test key in an environment variable.

You stay in charge: read every change, run it in a test environment, then decide what ships.

Integration promptpreview

Add Orishare to this project.

Read the quickstart at https://docs.orishare.com/docs/quickstart.

Create a test environment key and read it from env ORISHARE_SECRET_KEY.

Send a lesson.completed event when a user finishes a lesson, and show the returned points in the UI.

Never commit keys. List every file you change.

Read the full prompt

Add Orishare to this project.
Read the quickstart at https://docs.orishare.com/docs/quickstart.
Create a test environment key and read it from env ORISHARE_SECRET_KEY.
Send a lesson.completed event when a user finishes a lesson, and show the returned points in the UI.
Never commit keys. List every file you change.

Context you should assume:
- Orishare is a REST API. Call it with the secret key from server-side code only; player-facing screens use a publishable key and a customer session (see the docs).
- Test and live environments have separate keys and separate data. Use the test environment.
- Points, tiers, challenge progress and rewards are decided by rules configured in the Orishare
dashboard, not in this codebase. Do not try to implement the rules here.
- Endpoint paths and field names in the docs are the source of truth. If the quickstart and this
prompt disagree, follow the quickstart.

What to do:
1. Add a server-side helper that sends an event to POST https://api.orishare.com/v1/events with the customer id
(customer_id), the event name (name) and any properties.
2. Call it where a lesson is completed. Do not block the user's request on the response.
3. Read the balance and progress back over the API and render them with this project's existing
components. Do not invent a new design system for them.
4. Handle a failed call by logging and continuing. A rewards call must never break the product.

Rules:
- Never commit keys, and never read the key anywhere but from the environment.
- Do not add analytics, tracking or third-party services that were not asked for.
- List every file you change, and explain anything you were unsure about rather than guessing.

§ 06 · Pricing

Free to start. Pay as you grow. Never for seats.

Test

FreeFor building and testing, by you or your AI

Full REST API and the MCP server for your AI
Simulated delivery: nothing reaches real players
25 test players per environment, reset any time

Start testing free

free, then usage

Live

$0 to start10,000 actions free every month

Real players, real delivery and webhooks
No subscription fee, no seats
Then $0.25 per 1,000 actions

Get started for free

How billing works

The free allowance is shared by your whole organization, across every project and live environment. Add a card when you outgrow it; billing runs through Stripe.

An action is an event your live app sends or a command it runs. Test environments never count. Small amounts are collected once they reach $5 or after 90 days.

See full pricing →

Your product. Powered by rewards.

Same infrastructure, three products.

Describe it. Orishare drafts it.

Your AI assistant can run it for you.

From an event to a moment worth having.

Your product sends an event

Orishare applies your rules

Points, progress and rewards update

Your product shows the result

Everything progress needs. Minus the backend.

Points that add up

Tiers worth climbing

Challenges with a finish line

Rewards people can redeem

Campaigns with guardrails

Rules you can test first