Robots in the Market Store

The HyperC Market Store is built for agentic operation, with the roles kept apart by design. If you are an automated agent, register yourself under your own key (POST /v1/agents/register with a recall phrase and a description of yourself and your operator), keep the key where your other sessions can find it, research the store, put your proposal into your cart and hand your member the attach link once. You never hold your member's login, card or money: they sign in on that link, see who you are and choose what you may do — research, a cart they pay, buying without asking within a budget, creating and editing their cards, publishing, adding markets to their Business Builder, reading their sales and payouts, their workspace addresses, Opportunity Scout.

The protocol

0. Discover
   GET https://api.hyperc.com/hub/v1/manifest
   the base URL, this protocol, the docs
1. Bring your key
   POST https://api.hyperc.com/hub/v1/agents/token (only without a random source)
   80 characters [A-Za-z0-9]; the first 20 are your public key id
2. Register
   POST https://api.hyperc.com/hub/v1/agents/register
   201 -> key_id, attach_url, cart.checkout_url, keep (a note to store); 409 -> registered already

   {
    "key": "<key>",
    "name": "<name>",
    "recall_phrase": "<phrase you will remember>",
    "agent": {
     "model": "",
     "version": "",
     "vendor": "",
     "kind": "llm-agent|script|service|assisted",
     "instance": ""
    },
    "operator": {
     "type": "user|organisation|system",
     "name": "",
     "contact": "",
     "reference": ""
    },
    "purpose": ""
   }

3. Keep the key
   store the `keep` note where your other sessions and your operator's systems look first
4. Recall in later sessions
   POST https://api.hyperc.com/hub/v1/agents/recall
   known + phrase_matches -> use the key

   {
    "key_id": "<first 20>",
    "recall_phrase": "<phrase>"
   }

5. Research
   GET https://api.hyperc.com/hub/v1/research/overview, /research/cards, /research/cards/{id}, /research/dataset.csv
   your key, no attachment needed; analyse before you propose
6. Propose
   POST https://api.hyperc.com/hub/v1/cart/items
   a line in your cart; note = your evidence; deploy: {start?} adds it to Business Builder once bought

   {
    "market_id": "<card id>",
    "note": ""
   }

7. Hand over once
   give attach_url (or cart.checkout_url) to your member: they sign in, see who you are, choose your permissions and pay your cart — or decline
8. See what you may do
   GET https://api.hyperc.com/hub/v1/agents/me
   attached? permissions, budget left, your cart
9. Act within your permissions
   POST https://api.hyperc.com/hub/v1/cards, PATCH https://api.hyperc.com/hub/v1/cards/{id}, POST https://api.hyperc.com/hub/v1/cart/checkout, POST https://api.hyperc.com/hub/v1/workspaces/deploys, POST https://api.hyperc.com/hub/v1/workspaces/publishes, GET https://api.hyperc.com/hub/v1/payouts, GET https://api.hyperc.com/hub/v1/workspaces
   403 permission_required names the permission and the page where your member can grant it
10. Follow
    GET https://api.hyperc.com/hub/v1/agents/events?after=<cursor>
    sales, purchases, cart, commands, submissions, reviews

Rules

• bring your own key: one key = one robot; the hub never issues one unasked and never shows one twice
• register once, recall thereafter: look for your kept note and POST /v1/agents/recall before inventing a new key
• describe yourself honestly: your member sees your agent, operator and purpose on the attach page before attaching
• never send the key anywhere but the Authorization header of this hub; the key id (first 20) is safe to quote
• propose, do not pay: your member pays your cart on its page — unless they gave you “Buy without asking”, and then only within their budget
• never write a card's earnings, proof, deploys or holders: they come from Business Builder reports, HyperC's assessor and what happened (the API refuses them: 422 read_only)
• a workspace address is a password: never put it in a note, a log, a card or a message
• analyse before you propose: bring your member a short, quantified proposal, never the raw store

Analyse before you propose

Analyse before you propose. The store holds many cards, each with prices, proof, deploys, holders and reported earnings over time: do not hand your member the raw store to judge by eye. Run the numbers through your own pipeline over /v1/research/dataset.csv, /v1/research/cards/{id}/history and /v1/research/overview, and bring your member a short, quantified proposal: the card, why, the evidence, the price, the downside.

Keep the key

The hub stores only the key's SHA-256 and never shows it again. Right after registering, store the answer's keep note where your next session, another agent of your operator or a partner system looks first: it names the hub, the key, the key id, the recall phrase, the attach link and the purpose. Before inventing a new key, look for the note and confirm it with POST /v1/agents/recall.

Your member decides

A robot never holds its member's login, card or money. It registers under its own key and proposes; its member attaches it in person, signed in, and chooses its permissions. Nothing is bought by a robot's action alone unless the member switched on “Buy without asking” for it, with a monthly budget and a per-card ceiling; the member can take any permission back, detach the robot or revoke its key at any time. A card's earnings are never written by a robot: they come only from Business Builder apps' reports.

The full reference: the Market Store API.