Skip to main content
GET
/
v1
/
lookup-entity
/
{kernel_id}
Lookup entity
curl --request GET \
  --url https://api.kernel.ai/rest/v1/lookup-entity/{kernel_id} \
  --header 'x-api-key: <api-key>'
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "completed",
  "created_at": "2025-06-05T12:00:00Z",
  "completed_at": "2025-06-05T12:00:05Z",
  "record": {
    "kernel_id": "6347422643",
    "entity_type": "legal_entity",
    "legal_info": {
      "country": "US",
      "reasoning": "Confirmed via Stripe terms of service page.",
      "brand_name": "Stripe, Inc.",
      "confidence": "HIGH",
      "legal_name": "Stripe, Inc.",
      "website": "https://stripe.com"
    },
    "brand_info": {
      "country": "US",
      "website": "https://stripe.com",
      "reasoning": "Primary brand site confirmed via domain ownership.",
      "brand_name": "Stripe",
      "confidence": "HIGH"
    },
    "entity_classification": {
      "type": "Company",
      "subtype": "Operating",
      "reasoning": "Classified as an operating company based on commercial activity."
    }
  }
}
Returns the latest completed entity resolution result for the given kernel_id. This is a synchronous lookup — no job creation or polling required. Use the kernel_id from a previous Resolve entity call to retrieve stored entity data without resubmitting the company details.
This endpoint only returns completed entity resolution results. If no completed resolution exists for the given kernel_id, it returns a 404. To resolve a new entity, use the Resolve entity endpoint.The response includes entity-level data only. Per-customer fields like entity_resolution_confidence and entity_resolution_reasoning are not included — those are specific to each resolution request and are available via the Get entity resolution result endpoint.

​
Examples

​
Lookup a resolved entity

curl
curl https://api.kernel.ai/rest/v1/lookup-entity/6347422643 \
  -H "x-api-key: $KERNEL_API_KEY"
Response (200)
{
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "status": "completed",
  "created_at": "2025-06-05T12:00:00Z",
  "completed_at": "2025-06-05T12:00:05Z",
  "record": {
    "kernel_id": "6347422643",
    "entity_type": "legal_entity",
    "legal_info": {
      "country": "US",
      "reasoning": "Confirmed via Stripe terms of service page.",
      "brand_name": "Stripe, Inc.",
      "confidence": "HIGH",
      "legal_name": "Stripe, Inc.",
      "website": "https://stripe.com"
    },
    "brand_info": {
      "country": "US",
      "website": "https://stripe.com",
      "reasoning": "Primary brand site confirmed via domain ownership.",
      "brand_name": "Stripe",
      "confidence": "HIGH"
    },
    "entity_classification": {
      "type": "Company",
      "subtype": "Operating",
      "reasoning": "Classified as an operating company based on commercial activity."
    }
  }
}
Response (404) — entity not found
{
  "error": "Entity not found"
}
For the full result schema, see Completed result.

Authorizations

​
x-api-key
string
header
required

Include your API key in the x-api-key header.

Path Parameters

​
kernel_id
string
required

The kernel_id of a resolved entity

Example:

"6347422643"

Response

Completed entity resolution result

​
id
string
required

Unique identifier for the job that produced this result.

Example:

"550e8400-e29b-41d4-a716-446655440000"

​
status
enum<string>
required

Always completed for lookup results.

Available options:
completed
​
created_at
string<date-time>

ISO 8601 timestamp when the job was created.

Example:

"2025-06-05T12:00:00Z"

​
completed_at
string<date-time>

ISO 8601 timestamp when the job reached a terminal state.

Example:

"2025-06-05T12:00:05Z"

​
record
object

Entity-level data. Per-customer fields like entity_resolution_confidence and entity_resolution_reasoning are not included in lookup results.