Standard
A Standard is a spec an Interface conforms to, so a Startup may publish its Product’s Verbs in a shape outside callers already use.
Properties
| Property | Type | Required | Description |
|---|---|---|---|
spec | url | required | The published specification its translator implements. |
path | string | required | Where its translator answers on an Interface, such as / or /. |
operations | string[] | required | The operations its translator accepts; a Startup maps each one onto one of its own Verbs. |
Object
{
"$id": "https: //api.sb/ patentpad.com/ standards/ standard_1",
"$type": "Standard",
"spec": "https: //patentpad.com",
"path": "/",
"operations": [
"chat.completions.create"
]
}Relationships
- A Standard spoken by many Interfaces: Callers in a Standard’s shape reach the Interface’s Verbs through the platform’s one translator for that Standard.
spokenBy, inversespeaks.
Verbs
getReturns one Standard by id.GET /{namespace}/standards/{id}listReturns Standards, newest first, one page at a time.GET /{namespace}/standards
A Standard is kept forever and never edited: it has no update or delete.
Permissions
Which Access level may call each Verb. One-way Verbs wait their delay window.
| Operation | owner | admin | member | viewer |
|---|---|---|---|---|
Standard.get | Yes | Yes | Yes | Yes |
Standard.list | Yes | Yes | Yes | Yes |
Call it
Show me the latest standard.Example
listsmith.ai maps the openai-chat Standard's chat.completions.create operation onto its own Listing.write Verb. A Customer's existing model client then calls https: and gets a listing back in the shape it expects.