The route
- Fetch the public catalogue.
- Read each tool’s execution and render metadata.
- Group by category and link to the canonical interface.
- Keep source links and refresh the catalogue with its cache validators.
Keep this boundary in your build
Browser tools execute at their declared interface; the catalogue API does not run tool inputs.
Start with this call
Request
This operation declares public access.
curl 'https://ursy.io/wp-json/ursy-tools/v1/catalog?view=summary' \
-H 'Accept: application/json'- Scopes
- None declared
- Execution
- At the owning service
- Risk classification
- not declared
Parameters
category query · string See the accepted schema for constraints.
view query · string See the accepted schema for constraints.
TRY A PUBLIC READ
Make a live request.
Runs a bounded GET against ursy.io. No credentials are sent.
Response schemas and request body
{
"requestBody": null,
"responses": {
"200": {
"description": "A public JSON response.",
"headers": {
"Cache-Control": {
"schema": {
"type": "string"
}
},
"ETag": {
"schema": {
"type": "string"
}
},
"X-Ursy-Instrument": {
"schema": {
"type": "string"
}
}
},
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/CatalogEnvelope"
}
}
}
},
"404": {
"description": "A stable error envelope.",
"headers": {
"Cache-Control": {
"schema": {
"type": "string"
}
},
"ETag": {
"schema": {
"type": "string"
}
},
"X-Ursy-Instrument": {
"schema": {
"type": "string"
}
}
},
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/ErrorEnvelope"
}
}
}
}
}
}