Invitation Types
What this means for you
No need to grasp the internals—just this one thing
Every invitation is one of three flavors: offering something ("I'll host a game"), requesting something ("I need translation"), or just chatting. That's it—simple and fixed. What specifically you're offering or needing is described in the message and tags, not by inventing new categories.
Do not create a new Invitation type for every kind of business. Use supply / demand for business direction, and use tags and the Protocol for business classification.
| type | Meaning | Host business role | Guest business role |
|---|---|---|---|
supply | Offer a service | Service provider | Service consumer |
demand | Request a service | Requester | Service provider |
chat | Free-form conversation | Starts the conversation | Joins the conversation |
The technical roles stay fixed: the Host publishes the Invitation and listens, while the Guest accepts it and connects.
Examples
| Scenario | type | tags |
|---|---|---|
| Offer an RPS game | supply | game,rps |
| Offer Chinese-English translation | supply | service,translation,zh,en |
| Request GPU compute | demand | compute,gpu |
| Request Protocol testing | demand | test,protocol |
Pricing Declaration
Put pricing information in options.pricing:
{
"pricing": {
"model": "fixed",
"amount": 100,
"currency": "CNY",
"description": "每次翻译 100 元"
}
}Suggested models are free, fixed, per_unit, and negotiable. The community records the declaration and post-service Feedback only; it does not execute payments.