Pack builder quickstart

We turned jurisdiction, hardware protocols and SaaS APIs into drivers.

You build packs that translate events into local rules. We handle billing, identity, compliance and distribution. You keep 50% of every workspace that uses your pack.

Start with $5 credits, about 50,000 calls. One call = $0.0001.

Create sandbox + get $5 credits Run first example in sandbox

Copy and run

curl -s https://robo-meister.com/api/v1/workflows.json -H "Authorization: Bearer $TOKEN" # cost $0.0001

If you need a token first, jump to Authentication.

Free start

Start in sandbox with concrete credits, then turn packs into revenue.

Every new org gets $5, about 50k calls. 1 call = $0.0001. Check live balance at /portal/credits. When you publish a pack, credits become revenue.

1. Starter grant

Credits are issued to the organisation with an expiry, eligible meters, and anti-abuse rules.

2. Sandbox token

Use least-privilege test access for quickstart calls and demo data.

3. Metered checks

Metered operations should reserve credits before work and settle actual usage after completion.

4. Production gate

Go live only after identity, terms, token scope, webhook, billing/free-tier, and smoke checks pass.

Credits calculator

Slide expected calls per day to estimate API cost and pack revenue at $19/month installs with a 50% share.

Calls / day

Monthly calls

Monthly cost

Open portal free-start setup See production checklist

Choose your path

From first response to first workflow in one day.

5-minute path

Call GET /api/v1/workflows.json with a bearer token and confirm auth.

30-minute path

Send an event, register a webhook endpoint, and inspect the response payload.

1-day path

Install a package, run one workflow, and agree on trace IDs, retries, and ownership.

Sandbox copy block

export TOKEN="paste-test-token-here"
curl -s https://robo-meister.com/api/v1/workflows.json \
  -H "Authorization: Bearer $TOKEN"

Use a portal-issued test token. Do not paste production credentials into demos or ads.

Quickstart

Create token → call endpoint → post first event.

Step 1

Get API access

Open the portal, create or select your org, then generate a Personal Access Token.

Authorization: Bearer <TOKEN>

Token setup details

Step 2

Make first authenticated call

curl -s https://robo-meister.com/api/v1/workflows.json \
  -H "Authorization: Bearer $TOKEN"

This confirms auth and endpoint reachability.

Step 3

Send first event

curl -X POST https://robo-meister.com/api/v1/events.json \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"event_type":"task_completed"}'

First integration checklist

Create account or sign in via portal start.
Create token in portal API access area.
Install SDK (PHP/Java/Python) from the matrix below.
Make your first authenticated API call.
Register webhook endpoint and validate signature handling.
Check credits/usage in portal credits.

Live examples

Run pack-starter examples in your sandbox.

Examples load from robo-meister/pack-starter/examples/*/portal.json; if GitHub or the endpoint is unavailable, the page uses the bundled mock.

SDK matrix

Start with the core Robo Connector package, or pick a focused PHP SDK for Store, identity/intent validation, OCR, context, or signatures.

Recommended core

PHP Robo Connector SDK

App Store and external service integrations.

composer require robo-meister/robo-connector-api

Open on Packagist

Java SDK

Use the Java SDK module in this repo.

Repo/docs link

Python SDK

pip install robo-connector-sdk

Repo/docs link

PHP SDK family on Packagist

Install the package that matches the API surface you are integrating.

View all Robo Meister packages

Robo Store API

Store API SDK for commerce and marketplace flows.

composer require robo-meister/robo-store-api

Packagist package

FlowBeacon API

Validate Robo account JWTs and intent contexts.

composer require robo-meister/flow-beacon-api

Packagist package

FlowScribe OCR API

Connect document and OCR flows to FlowScribe.

composer require robo-meister/flow-scribe-api

Packagist package

Context Engine API

Read and write Context Engine keys and processing state.

composer require robo-meister/context-engine-api

Packagist package

AccordFlow Signature API

Connect lightweight electronic signature workflows.

composer require robo-meister/accord-flow-api

Packagist package

Authentication

Use Bearer tokens for scripts and OAuth 2.0 for user-consent app flows.

Personal Access Token

Generated in the portal for an organization
Scope by module permissions
Rotate/revoke at any time

Authorization: Bearer <TOKEN>

OAuth 2.0

Authorization Code and Client Credentials
Tenant-aware consent screens
Refresh tokens for long-lived sessions

POST /oauth/token
client_id=...&client_secret=...
grant_type=client_credentials

REST API Basics

Base URL, common endpoints, pagination, and error format.

Base URL

https://robo-meister.com/api/v1

Examples

GET /workflows.json
GET /workflows.csv
POST /events.json

Querying + errors

GET /clients.json?status=active&page=2&limit=50
GET /products.json?category=hardware&sort=-createdAt

{
  "status": "error",
  "error": {"code": "invalid_scope", "message": "Token lacks finance:read"}
}

Production readiness

Do not move live traffic until these checks are green.

Verified organisation

Email, organisation profile, accepted terms, and owner contact are complete.

Scoped live token

Production credentials use only the scopes needed by the integration.

Credits or approved free tier

Live calls have billing, top-up, or a documented free-tier entitlement.

Webhook reliability

Callbacks verify signatures, retry safely, and dedupe event IDs.

Idempotent writes

State-changing calls send an Idempotency-Key and tolerate replay.

Smoke test passed

A final live-mode smoke request is logged with trace ID and owner.

Runtime contract

Errors, rate limits, idempotency, and credits should be predictable.

Standard error shape

{
  "status": "error",
  "error": {
    "code": "insufficient_credits",
    "message": "Starter credits are exhausted.",
    "remediation_url": "/portal/credits",
    "trace_id": "req_..."
  }
}

Required headers for reliable writes

Authorization: Bearer $TOKEN
Idempotency-Key: order-123-run-1
X-Robo-Environment: sandbox
X-Robo-Trace-Id: client-generated-trace

Responses should include rate-limit and credit balance hints whenever possible.

Webhooks & Events

POST /webhooks.json
{
  "url": "https://example.com/webhooks/robo",
  "events": ["invoice.created", "shipment.updated"],
  "secret": "<HMAC_SECRET>"
}

Signature + topics

X-Robo-Signature: t=1733826000,v1=hex(HMAC_SHA256(body, secret))

events_channel:user:<id>:task_completed
events_channel:organization:<id>:inventory_update

Package Distribution

Ship apps, workflows, drivers, and integrations as .rappkg archives.

Structure

my-first-app.rappkg
├── meta.json
├── app.json
├── workflows/
├── drivers/
└── integrations/

POST /packages/install.json
{ "package_url": "https://.../my-first-app.rappkg" }

Minimal meta.json

{
  "name": "my-first-app",
  "version": "1.0.0",
  "type": "app",
  "entry": "app.json"
}

Context Engine

Use hierarchical context keys and queue patterns once your first integration is running.

Key patterns

Context:User:<user_id>:Project:<project_id>:client
Data:Queue:<queue_id>:In:<type>:payload
Data:Queue:<queue_id>:Result:status

Processing flow

PUSH Data:Queue:plan-42:In:orders
SUB  Data:Queue:plan-42:Result:status

Advanced architecture and module docs

Reference these after onboarding: specialized module guides, integration hub, assistant docs, JSON samples, and deeper Context Engine material.

Context Engine Deep Dive

Resources

Partner materials for deeper planning.

Download the original partner PDFs after you have tested the pack-builder path.

Open full partner page

PDF Open PDF

Partner Quick Overview

Short introduction for first partner conversations.

PL PDF EN PDF

PDF Open PDF

Partner Business Guide

Detailed guide explaining partner models, cooperation paths, pilot flow, and objections.

PL PDF EN PDF

PDF Open PDF

Solution Catalog

Catalog of solutions, packages, modules, and first workflow examples for client conversations.

PL PDF EN PDF