Confidence in a classification
High, medium and low are grades indicating how strongly the listing supports its category. They are not numerical probability estimates.
All Cloud services
Classify events for search and filters.
Send an event’s name and any other details you have. Classify identifies what kind of event it is, such as a soccer match, a concert or a workshop, and returns categories and tags your application can use to organize listings and help people find them.
curl https://api.cloud.gomry.com/v1/classify \
-H "Authorization: Bearer $GOMRY_CLOUD_KEY" \
-H "Content-Type: application/json" \
-d '{
"events": [{
"name": "Electronic music DJ night",
"description": "Electronic music with guest DJs."
}]
}'Organize events with shared categories.
An event-discovery app may receive a DJ set, a soccer fixture and a musical with very different descriptions. Classify maps listings to a shared two-level taxonomy, with category IDs such as music.electronic, sports.soccer and performing_arts.musical, rather than relying on each publisher’s tags.
The result includes the display path, gathering format, attendance mode, language and search terms. Audience and holiday attributes add context when the listing supports them. Each result identifies its taxonomyVersion, so your application can keep category mappings tied to the version that produced them.
Send the listing, not just its web address.
{
"events": [
{
"id": "listing-1",
"name": "Electronic music DJ night",
"description": "An evening of electronic music performed by guest DJs.",
"attendance": "in_person"
}
]
}- Your ID
- listing-1
- Primary category
- music.electronic
- Confidence
- high
The category gives your application a consistent place for the listing in its music filters. Only the name is required; more listing information gives the classifier more evidence. Your own tags are hints rather than mandatory categories. Results return in request order and echo your ID.
Classify does not read a URL’s page. If the listing is still on a website, extract the fields with Scrape first. If you need to assemble a fuller event record from a URL or loose text, Events includes classification in its enrichment result.
Understand uncertain and missing results.
No supported classification
Test data or gibberish can return not_an_event. A listing that may describe a real event but supplies too little information can return insufficient_information. Your app can route those records for review instead of putting them into a plausible-looking category.
Classify uses Gomry’s event taxonomy. It is not a general-purpose classifier for unrelated industries or a way to upload a custom taxonomy.
A flat rate for each event processed.
| Operation | Rate | Unit |
|---|---|---|
| Classify an event | 0.8¢ | Per event processed by the model |
One request accepts 1–25 events. An item that fails before reaching the model is not charged, and an individual failure does not fail the rest of the batch.
Build with Classify.
Enable Classify for the project and grant classification permission to a Gomry Cloud key. Send a Bearer-authenticated request to POST /v1/classify. Read the service details under Services in the Cloud console.