hypergriiiiid - #282
Conversation
here we go
| Providers compete on price and quality. | ||
|
|
||
| **Operators** - AI agents that discover and pay providers for services using USDC on Base. | ||
| Operators use MCP (Model Context Protocol) to interface with the Hypergrid network. |
There was a problem hiding this comment.
Recommend linking here to https://modelcontextprotocol.io, e.g. something like
Operators use [MCP (Model Context Protocol)](https://modelcontextprotocol.io) to ...
| @@ -0,0 +1,106 @@ | |||
| # Running an Operator Node | |||
|
|
|||
| The Hypergrid protocol allows for *Operators* to make micropayments in USDC on the Base blockchain in exchange for services from *Providers*. | |||
There was a problem hiding this comment.
I think I see "Base blockchain" used more, and it's a little clearer to someone who might not know what an L2 is. Going to submit a version without this change, we can go in the other direction if you feel strongly about it
| **2. Install Operator Client** | ||
|
|
||
| Once your node is booted, you'll be able to access the home screen, and from there you can navigate to the App Store. | ||
| This is an onchain registry of Hyperware applications similar to Hypergrid. |
There was a problem hiding this comment.
nit:
Hyperware applications similar to Hypergrid. -> Hyperware applications, including Hypergrid.
|
|
||
| **1. Get a Hyperware node** | ||
|
|
||
| The Hypergrid Provider clent is built on top of Hyperware, a p2p application deployment platform, so in order to act as a provider you'll need to be runnning a Hyperware node. |
There was a problem hiding this comment.
runnning has an extra n:
-> running
| **1. Get a Hyperware node** | ||
|
|
||
| The Hypergrid Provider clent is built on top of Hyperware, a p2p application deployment platform, so in order to act as a provider you'll need to be runnning a Hyperware node. | ||
| The simplest way to obtain a running node is through our hosting solution, Valet, where we will run your node for you. |
There was a problem hiding this comment.
nit: obtain a running node -> obtain a node
|
|
||
| The `~description` and `~instructions` notes merit deeper thought. | ||
| A description is how an agent will find your Provider. | ||
| If an agent with access to Hypergrid stumbles into a scenario where it thinks it might benefit by calling a Provider (maybe it doesn't have access to some data, wants to double check something specific, or needs a tool its local client doesn't have installed), it will search the Hypergrid registry and it will use the description field to do so. |
There was a problem hiding this comment.
Can make less wordy like:
... access to Hypergrid thinks it might benefit by calling a Provider ...
| It's possible to update this later, so be thoughtful but don't stress it too much. | ||
|
|
||
| Instructions tell the agent how to format a call to your provider. | ||
| You should be as detailed as possible so it "just works", notice how our weatherapi Provider has basically the entire call structure written out. |
There was a problem hiding this comment.
We should provide one or both of:
- Example(s) of good / bad description/instructions
- Links to docs discussing how to make good description/instructions
There are a bunch of example MCP servers here: https://modelcontextprotocol.io/examples
but it requires clicking into the repos and looking at the files, e.g. https://github.com/modelcontextprotocol/servers/blob/d2b217ac4fb5d2b4c0ca60af5ca9ca7e6be0082e/src/filesystem/index.ts#L446-L555
and it might be confusing because there is more going on here than just description/instructions
I don't think this one is blocking, but I do think it is important (otherwise these directions are pretty abstract)
There was a problem hiding this comment.
The photo linked there includes an example set of instructions, or should anyway.
|
|
||
|
|
||
|
|
||
|
|
| Hit the Register Provider Configuration button, and you're almost ready to go. | ||
|
|
||
| In the future, this will prompt you to sign a transaction in order to directly mint your Provider onchain. | ||
| To prevent spam while Hypergrid is in beta, we're using a Solana-style "proof of discord" mechanism: hit the copy button to copy the metadata for your provider, and link it to us in the provider-registration channel of the [Hyperware discord](https://discord.com/invite/KwNE58RKpg). |
There was a problem hiding this comment.
This could be simplified (i.e. probably remove solana reference)
There was a problem hiding this comment.
LMFAO I forgot to delete that. Yes definitely should not make it through.
| Hit the Register Provider Configuration button, and you're almost ready to go. | ||
|
|
||
| In the future, this will prompt you to sign a transaction in order to directly mint your Provider onchain. | ||
| To prevent spam while Hypergrid is in beta, we're using a Solana-style "proof of discord" mechanism: hit the copy button to copy the metadata for your provider, and link it to us in the provider-registration channel of the [Hyperware discord](https://discord.com/invite/KwNE58RKpg). |
There was a problem hiding this comment.
Is there a problem here where users' API keys will be exposed when they post in the discord?
There was a problem hiding this comment.
No, and I should clarify that. What I'm asking them for is the metadata that would go onchain anyways, but we haven't set up permissionless registration yet, so proof-of-discord seemed expedient.
meep
2 participants
Slight reformatting of docs, adds Hypergrid documentation. LGTM