Provided by Crustdata
Resolve Company Names, Domains or LinkedIn URLs to Company Records (Crustdata)
Resolve up to ten companies at a time from a messy company name, a website domain or a LinkedIn company URL into Crustdata company records, ranked by a confidence score, each with its Crustdata identifier and basic profile. Give exactly one kind of identifier per call — names, domains or URLs, never a mixture. Use it to clean an inbound list before paying for the full record lookup.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"names": {
"type": "array",
"items": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"maxItems": 10,
"minItems": 1
},
"fields": {
"type": "array",
"items": {
"enum": [
"crustdata_company_id",
"basic_info",
"social_profiles"
],
"type": "string"
},
"maxItems": 3,
"minItems": 1
},
"domains": {
"type": "array",
"items": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"maxItems": 10,
"minItems": 1
},
"exact_match": {
"type": "boolean"
},
"professional_network_profile_urls": {
"type": "array",
"items": {
"type": "string",
"maxLength": 300,
"minLength": 1
},
"maxItems": 10,
"minItems": 1
}
},
"additionalProperties": false
}{
"fields": [
"crustdata_company_id",
"basic_info"
],
"domains": [
"stripe.com"
]
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.mdThen ask for this Endpoint:
Run the Crustdata Endpoint /company/identify on Glasser with input {"fields":["crustdata_company_id","basic_info"],"domains":["stripe.com"]}glasser run -p crustdata -e '/company/identify' -i '{"fields":["crustdata_company_id","basic_info"],"domains":["stripe.com"]}' --endpoint-version 1Pinned to version 1, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"crustdata","endpoint":"/company/identify","input":{"fields":["crustdata_company_id","basic_info"],"domains":["stripe.com"]},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Pinned to version 1 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.00 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |