Use PULSE for AI. Reveal token rewards.

Start here

Connect a wallet on Robinhood Chain, create a key, and choose how much PULSE to lock. Confirm the wallet transactions and wait for activation. Once activation completes, copy your key and confirm you have saved it.

Holding PULSE or creating an unused key does not earn rewards.

Keys & Studio

A normal OpenRouter key

For managed keys, select OpenRouter in your app and paste the key you copied from Pulse. There is no custom URL to enter. Your app must support OpenRouter and the model or modality you want to use.

Pulse funds the upstream OpenRouter account and creates a separate, capped key for you. Your wallet’s PULSE lock backs that key’s allowance. The management credential stays on Pulse’s server.

Generate inside Pulse

Studio supports image and video generation through available models. Choose a model, add the references it supports, and enter your prompt. Price estimates update as you change settings; generation starts only when you submit.

Completed images and video-job references are saved in this browser. Download outputs you want to keep. A character-swap layout in a preview is not an available live model.

See your usage

Open a key’s Details to see Activity: model, time, outcome, token counts when reported, and estimated PULSE per call. Receipts can arrive after the balance changes. The key balance uses OpenRouter’s cumulative billed total; individual receipts do not charge you again.

Older gateway keys use Pulse’s OpenAI-compatible endpoint. They are not interchangeable with managed OpenRouter keys; newly configured managed-key deployments use the flow above.

How pricing works

Model prices are shown in PULSE. When a managed key is funded, its pricing terms are fixed for that key, and your locked PULSE sets its total inference allowance.

As OpenRouter reports spend, Pulse consumes the corresponding proportion of the lock. Amounts are rounded to token base units and never exceed that lock. Unused allowance is not a fee.

The Models page reads provider catalogue prices through Pulse’s pricing service. Studio estimates depend on your chosen settings; blue dots compare estimated cost per image or per second. Actual usage determines the final PULSE spent.

Reward eligibility is based on covered provider spend.

Closing & refunds

Close a key when you are finished. Pulse disables it at OpenRouter, confirms it has stopped, checks the latest usage, and returns unused PULSE through the escrow contract. Exhausted keys enter closure automatically.

Your refund progresses automatically through provider confirmation and the blockchain transfer. Follow its status in the app; a notification confirms when the return lands.

Pulse absorbs provider charges reported after the refund calculation; it does not take the refund back from you. If a required check fails, the system retries rather than presenting an unconfirmed transfer as complete.

Your refund and reward draw are separate. PULSE can be back in your wallet while the reward is still being prepared. The escrow also has a timeout-based owner exit for outages; it is not the normal refund path.

What decides your reward

Covered inference spend earns eligibility under the key’s versioned reward policy. After usage settles, Pulse commits the draw and policy against a future drand randomness round. Once that round arrives, the outcome is recorded.

Plinko reveals your recorded entitlement, one ball at a time. Replaying the animation or clicking again does not reroll the reward or increase it. Claiming sends each recorded token grant from the reward vault at most once.

Amounts follow the reward policy and outcome. V1 does not promise a dollar-for-dollar rebate, a fixed return, or future appreciation. Receipts show every awarded token and its actual quantity.

USD estimates appear only when an exact token market is configured and a recent price is available. Unpriced assets stay unpriced.

Where the funds come from

Robinhood Chain

PULSE locks, burns, unused-balance returns and token claims are recorded on chain.

Provider credit

Pulse funds OpenRouter credit. Your activated key uses a capped allowance backed by your PULSE lock.

Reward inventory

A separately funded vault holds reward tokens. Claims send your recorded allocation to your wallet.

Activation reserves provider budget and worst-case reward inventory before enabling a managed key. The server checks these budgets; the escrow records cumulative PULSE burns and refunds on chain.

Burning PULSE removes tokens from supply. It does not sell them for cash or refill OpenRouter credit. Provider credit and reward inventory need separate funding.

Trading-fee proceeds can fund these reserves through treasury operations. V1 does not automatically route launch fees into new pools, buy reward tokens, or use an LP as the inference vault.

What is v1 today?

V1 includes PULSE escrow, managed-key integration, usage accounting, closure and refund workers, committed reward draws, vault claims, and the Studio and Activity interface.

Live managed-key operation requires funded provider credit, reward inventory, a server-side management credential, and working usage-receipt delivery. Having an interface or a preview does not establish that a deployment is funded and enabled.

Future work

Custom Uniswap v4 pools, hooks that connect trading and settlement, and agent tooling are future directions. Hook contracts and experiments in this repository do not make those paths part of the current v1 launch. They are not required to use the vault-based flow described here.