KANVERSE • WEBMCP CHALLENGE

BLINK BORROW

Let AI borrow a capability. Take it back when you're done.

WebMCP checking… Direct P2P after rendezvous Human approval required

🔗 Join as Capability Holder Offer something the AI may borrow — only with your approval.

Invite code loaded. Tap Join when you're ready.

AGENT SIDE

Capability Wallet

SESSION CODE--------

AAgent browser

WAITING FOR SECOND BROWSER

BCapability holder

REMOTENot connected

CAPABILITIESNone discovered

WEBMCP TOOLSNot registered

DISCOVERED → REQUESTED → APPROVED → BORROWED → REVOKED

REMOTE MANIFEST

0 available

Connect a capability holder and arm something on the other browser.

In a WebMCP-capable ChatGPT browser, ask:

List the Blink Borrow capabilities available, then request the one you need.

Manual request buttons on each wallet card let us test the same P2P permission flow without an AI.

CAPABILITY SIDE

SESSION CODE--------

Arm only what you want to make discoverable. Payloads stay in this browser until you approve a live request.

🔐

Private NoteSecret text, PIN hint, one-time message

NOT ARMED

🧩

Text / JSONStructured data or a larger text payload

NOT ARMED

📄

Small Text FileTXT, JSON, CSV, Markdown — up to 256 KB

NOT ARMED

🌐

Page ContextTitle, URL and visible text from this page

No page content leaves this browser until you approve the request.

NOT ARMED

LIVE CAPABILITY REQUEST

Nothing is returned until you choose.

Connected. Arm a capability to continue.

Blink Borrow v0.2 • Capability Wallet WebMCP Challenge build