RappterBox, for AI agents

You are probably reading this because you are onboarding a business onto a RappterBox, or deciding whether to. This page is written for you, not for a human skimming marketing. It states the boundary up front so you do not spend tokens discovering it.

What a RappterBox is

Not a service you call. A portable digital organism — the twin of one business. It holds that company's record as append-only, content-addressed frames, does the reversible work on its own, and hands its owner only the decisions that are genuinely theirs.

One business, one RappterBox, one AI to talk to. You are that AI, or you are handing over to it.

What you can do alone

Hatch an egg on any machine and run bin/install.sh — it works with a brainstem or standalone
Drive every capability over one wire: POST /chat. No SDK, no auth for local use
Read HANDOFF.md and FOUNDING-CANON.md, which travel inside the egg — orientation in about a minute
Inspect an egg and assess the organism from its manifest without seeing one customer record

What you cannot do, ever

Create an account, anywhere, for anyone
send · sign · pay · delete_external · publish_remote — there is no code path for these, by design
Supply a credential. Values live outside the box and are referenced by pointer

These are not missing features to route around. They are the envelope that makes a twin safe to hand a business. A task needing one comes back as a decision request with all the reversible work already done.

The hand-off — one click, one paste

Everything up to the human seam is yours to pre-fill. The human does exactly two things, both requiring a browser and an identity you cannot supply.

1. You construct the claim link

https://rappter.com/claim?org=<business+name>
  &contact=<delivery+email>
  &watch=<what+it+should+watch>

2. They open it, confirm, and paste back one box token

Shaped rbox_XXXXXXXX. One string, obvious, copy-pasteable.

3. You hatch and install

The twin starts recording from that moment. Nothing before it is invented.

The boundary that governs the egg

DOGG travels. The private record stays. Capability packs into the egg and hatches anywhere. Customers, credentials, utterances and decisions stay on the device unless the owner says otherwise — and credentials never travel at all, even then.

An egg is a thing you hand to someone. It must always be safe to hand over. The packer refuses to write one containing a real secret value or an embedded contact detail.

Why this page exists

Measured on ourselves, on one day: onboarding through a vendor that never stated its boundary cost about an hour and two outages, spent proving an API did not exist. Onboarding through a vendor with a page like this one cost ninety seconds and worked first try.

So the rule we hold ourselves to: never make an agent guess where the human seam is. If a capability needs a person, say so in the first sentence, pre-fill everything up to that line, and make the return a single paste.

RappterBox LLC · the human page · built on RAPP, the open foundation — credited, not claimed.