[ SYS_STATUS: OPERATIONAL ] — [ QUEUE_TOTAL: 0 ] — [ FUNDING_VOL: $0 ]

Developers · /developers

Program the outcome

Why integrate BTheHype? Because some valuable outcomes require verified human execution — and your product already knows when those outcomes should happen.

Bring Your Own Event. Your product detects user_activated. Your backend sends the track event. BTheHype handles execution and verification.

Admission is controlled. API key setup and destination integration are required after provisioning.

01

Define the outcome

Specify the desired human outcome your product needs — not just the action an Operator performs.

02

Create the Growth Program

Configure demand: outcome definition, eligibility rules, and execution funding in the Developer Console after admission.

03

Fund execution

Fund your Growth Program with HYPEIT (100 HYPEIT = $1 USD). Settlement occurs only on verified outcomes.

04

Send the event

Your backend POSTs to /api/v1/events/track when the outcome should be requested. You own the event — BYOE (Bring Your Own Event).

05

BTheHype routes execution

The protocol authenticates, matches the program, and routes to an eligible Operator in the regional node pool.

06

Destination verifies the outcome

For supported integrations, your product confirms the outcome via server-to-server postback.

07

Settlement occurs

HYPEIT settles the verified execution. Reputation updates for the Operator.

Protocol terminal · sample trace

> Sample settlement trace (post-verification)

> [DESTINATION] postback: user_activated

> Outcome verified · HYPEIT settlement recorded

> Verified outcome credited to Developer program

Event Tracking

Bring Your Own Event

Send track events from your backend when a human outcome should be requested. HYPEIT settles only after destination confirmation verifies the outcome — not on ingest or impressions. Full SDK packages and in-console configuration arrive after Developer admission.

POST https://api.bthehype.com/v1/events/track
Authorization: Bearer haas_live_xxxxxxxxxxxxxxxxx
Content-Type: application/json
Idempotency-Key: req_abc123

{
  "event_type": "user_activated",
  "verification_id": "usr_987654321",
  "timestamp": "2026-08-27T14:30:00Z"
}

→ 200 OK — event accepted, routing begins

Not every event type is supported today. Growth Programs require a verifiable outcome path.

Request AccessSee How It Works