> ## Documentation Index > Fetch the complete documentation index at: https://docs.hyperspell.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Entity Resolution Evidence > Return one bounded, coherent snapshot of structured resolution evidence. This is provenance for one canonical identity, not an entity-to-entity relationship graph. Both endpoint collections fail closed on overflow so a capped prefix can never be mistaken for a complete explanation. ## OpenAPI ````yaml https://api.hyperspell.com/openapi.json get /entities/{entity_id}/resolution-evidence openapi: 3.1.0 info: title: Hyperspell API summary: >- Hyperspell is the memory layer for AI apps and agents. Through the API, you can add memories, connect data sources to index them in real-time, and search memories with our natural language query engine. termsOfService: https://hyperspell.com/blog/tos contact: name: Hyperspell url: https://hyperspell.com/ email: hello@hyperspell.com version: 0.32.1 servers: - url: https://api.hyperspell.com description: Production security: [] paths: /entities/{entity_id}/resolution-evidence: get: tags: - entities summary: Get Entity Resolution Evidence description: >- Return one bounded, coherent snapshot of structured resolution evidence. This is provenance for one canonical identity, not an entity-to-entity relationship graph. Both endpoint collections fail closed on overflow so a capped prefix can never be mistaken for a complete explanation. operationId: >- get_entity_resolution_evidence_entities__entity_id__resolution_evidence_get parameters: - name: entity_id in: path required: true schema: type: string format: uuid title: Entity Id - name: X-As-User in: header required: false schema: anyOf: - type: string - type: 'null' description: >- Optionally set this header to act as a specific user when using an API Key, equivalent to first exchanging the API Key for a User Token title: X-As-User description: >- Optionally set this header to act as a specific user when using an API Key, equivalent to first exchanging the API Key for a User Token responses: '200': description: Successful Response content: application/json: schema: $ref: '#/components/schemas/EntityResolutionEvidenceResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - APIKey: [] components: schemas: EntityResolutionEvidenceResponse: properties: entity: $ref: '#/components/schemas/EntitySummaryResponse' records: items: $ref: '#/components/schemas/EntityRecordResponse' type: array title: Records assertions: items: $ref: '#/components/schemas/EntityResolutionAssertionResponse' type: array title: Assertions bounds: $ref: '#/components/schemas/EntityResolutionEvidenceBoundsResponse' type: object required: - entity - records - assertions - bounds title: EntityResolutionEvidenceResponse HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError EntitySummaryResponse: properties: id: type: string format: uuid title: Id type: type: string title: Type name: type: string title: Name status: $ref: '#/components/schemas/EntityStatus' created_at: type: string format: date-time title: Created At updated_at: type: string format: date-time title: Updated At type: object required: - id - type - name - status - created_at - updated_at title: EntitySummaryResponse description: Bounded list shape; potentially large profile data stays on detail. EntityRecordResponse: properties: id: type: string format: uuid title: Id entity_type: type: string title: Entity Type provider: type: string title: Provider workspace: anyOf: - type: string - type: 'null' title: Workspace external_id: type: string title: External Id display_name: anyOf: - type: string - type: 'null' title: Display Name email: anyOf: - type: string - type: 'null' title: Email aliases: items: type: string type: array title: Aliases resolution_status: type: string title: Resolution Status resolution_method: anyOf: - type: string - type: 'null' title: Resolution Method resolver_version: anyOf: - type: string - type: 'null' title: Resolver Version resolved_at: anyOf: - type: string format: date-time - type: 'null' title: Resolved At created_at: type: string format: date-time title: Created At updated_at: type: string format: date-time title: Updated At type: object required: - id - entity_type - provider - external_id - resolution_status - created_at - updated_at title: EntityRecordResponse EntityResolutionAssertionResponse: properties: id: type: string format: uuid title: Id left_record_id: type: string format: uuid title: Left Record Id right_record_id: type: string format: uuid title: Right Record Id verdict: type: string enum: - same - different title: Verdict method: type: string title: Method resolver_version: type: string title: Resolver Version created_at: type: string format: date-time title: Created At type: object required: - id - left_record_id - right_record_id - verdict - method - resolver_version - created_at title: EntityResolutionAssertionResponse EntityResolutionEvidenceBoundsResponse: properties: complete: type: boolean title: Complete record_limit: type: integer title: Record Limit assertion_limit: type: integer title: Assertion Limit records_returned: type: integer title: Records Returned assertions_returned: type: integer title: Assertions Returned reason: anyOf: - type: string enum: - record_limit - assertion_limit - type: 'null' title: Reason type: object required: - complete - record_limit - assertion_limit - records_returned - assertions_returned title: EntityResolutionEvidenceBoundsResponse ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError EntityStatus: type: string enum: - provisional - confirmed title: EntityStatus description: How strongly the entity's current identity has been established. securitySchemes: APIKey: type: http description: >- API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user. scheme: bearer bearerFormat: Bearer ````