Provided by Akta
Resolve a Company Name or Website Into Identity Records (Akta)
Resolve one company name or website into Akta's identity records: the rows are the companies Akta matched, each carrying the canonical company name, the domain and the Akta company identifier that every other Akta Endpoint takes as its input. One free-text query per request, and no paging — it looks a company up by what it is called or where it lives on the web, and it is the first call in any Akta workflow. Matching is fuzzy and gives no warning: a name or website that Akta does not hold can come back as a different company with a similar name or domain, so check each row's name and website against the company you mean before you pass its id on.
How to run it
Step 1Set up
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.md
Show me how to use the Akta endpoint /v1/company/search on Glasser.glasser run -p akta -e '/v1/company/search' -i '{"query":"stripe.com"}' --endpoint-version 3Uses endpoint version 3. Inspect the current price before running. 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":"akta","endpoint":"/v1/company/search","input":{"query":"stripe.com"},"endpoint_version":3}'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. Uses endpoint version 3; inspect the current price before running.
Step 2Try a specific example task
When you need to qualify potential customers, you might compare company information with your ideal-customer criteria to decide which accounts to research next.
Copy this prompt into your agent to review companies against your ideal-customer criteria.
Use akta:/v1/company/search on Glasser.
Check the returned company data against my ideal-customer criteria.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"maxLength": 300,
"minLength": 1
}
},
"additionalProperties": false
}{
"query": "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 pricing works
| Data returned or no match | The same price with or without matching data. | $0.00 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |