Properties
| Name | Type | Description |
|---|---|---|
| name | string | The name of your brand or company, as the classifier should use it. |
| description | string | A paragraph on what the company does. |
| useCases | array | Typical uses of the product. |
| accounts | object | Your company's accounts, so posts from them are recognized as yours. |
| website | stringnull | The company's website, as entered during onboarding. |
| competitors | array | Names of competitors, so the classifier knows when a post is about one of them. Often the same names as your competitor keywords. |
| guidelines | stringnull | Rules for the classifier in your own words, saying what is relevant to you and what never is, for example "questions about our SDK, never job ads". After the description, this has the most effect on s |
| context | string | Classifier input. Built from the other fields unless you write it yourself. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/rumoro-dev/json-schema/rumoro-dev-company-schema.json",
"title": "Company",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/rumoro-dev-company-api-openapi.yml#/components/schemas/Company",
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "The name of your brand or company, as the classifier should use it."
},
"description": {
"type": "string",
"description": "A paragraph on what the company does."
},
"useCases": {
"type": "array",
"items": {
"type": "string"
},
"description": "Typical uses of the product."
},
"accounts": {
"type": "object",
"properties": {
"x": {
"type": [
"string",
"null"
],
"description": "Your X handle, without @."
},
"linkedin": {
"type": [
"string",
"null"
],
"description": "Your LinkedIn page, as its slug or link."
}
},
"required": [
"x",
"linkedin"
],
"description": "Your company's accounts, so posts from them are recognized as yours."
},
"website": {
"type": [
"string",
"null"
],
"description": "The company's website, as entered during onboarding."
},
"competitors": {
"type": "array",
"items": {
"type": "string"
},
"description": "Names of competitors, so the classifier knows when a post is about one of them. Often the same names as your competitor keywords."
},
"guidelines": {
"type": [
"string",
"null"
],
"description": "Rules for the classifier in your own words, saying what is relevant to you and what never is, for example \"questions about our SDK, never job ads\". After the description, this has the most effect on scores."
},
"context": {
"type": "string",
"description": "Classifier input. Built from the other fields unless you write it yourself."
}
},
"required": [
"name",
"description",
"useCases",
"accounts",
"website",
"competitors",
"guidelines",
"context"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/rumoro-dev-company"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.