Provided by BuiltWith
Look Up the Canonical Technology Name From a Description (BuiltWith)
Look up the canonical component names BuiltWith uses from a plain description of what a tool does: each candidate carries a similarity score, its category and a short description of the technology. This is the naming step that makes an adopter lookup possible when all you know is what the technology does — feed the name it returns to the adopter list. A meaningless phrase still comes back with the nearest names at low scores, so read the score.
Contract snapshot: 2026-09-29. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"QUERY"
],
"properties": {
"LIMIT": {
"type": "integer",
"maximum": 100,
"minimum": 1
},
"QUERY": {
"type": "string",
"maxLength": 200,
"minLength": 2
}
},
"additionalProperties": false
}{
"QUERY": "headless commerce"
}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 BuiltWith Endpoint /vector/v1/api.json on Glasser with input {"QUERY":"headless commerce"}glasser run -p builtwith -e '/vector/v1/api.json' -i '{"QUERY":"headless commerce"}' --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":"builtwith","endpoint":"/vector/v1/api.json","input":{"QUERY":"headless commerce"},"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 |