> ## Documentation Index > Fetch the complete documentation index at: https://docs.humanos.tech/llms.txt > Use this file to discover all available pages before exploring further. # Resolve Action > Resolve an action URN into its definition: name, description, declared parameters and the policy rules behind it. Snapshot and window bodies report per-action figures keyed by URN. The URN alone is a pointer; this endpoint tells you what an execution of that action actually permits. Use your own organization DID in `orgDid` to resolve your actions. Use a partner organization's DID to resolve theirs; this requires an active sharing grant from that organization, otherwise the request returns 404. See [Risk metrics](/essentials/risk-metrics) for how sharing grants let you consult another organization's intelligence. ## OpenAPI ````yaml /versions/2026-10-16.yaml get /intelligence/action openapi: 3.1.0 info: title: Humanos API description: Humanos API version: '1.0' contact: {} servers: - url: https://api.humanos.tech security: [] tags: - name: humanosApp description: '' paths: /intelligence/action: get: tags: - Intelligence summary: Resolve Action description: >- Resolve an action URN into its definition: name, description, declared parameters and the policy rules behind it. Snapshot and window bodies report per-action figures keyed by URN. The URN alone is a pointer; this endpoint tells you what an execution of that action actually permits. Use your own organization DID in `orgDid` to resolve your actions. Use a partner organization's DID to resolve theirs; this requires an active sharing grant from that organization, otherwise the request returns 404. See [Risk metrics](/essentials/risk-metrics) for how sharing grants let you consult another organization's intelligence. operationId: intelligence_action parameters: - name: orgDid required: true in: query description: >- DID of the organization whose data is consulted. Your own organization DID needs no grant; any other requires an active sharing grant from that organization to yours. schema: example: did:web:org-a.example type: string - name: urn required: true in: query description: >- URN of the action version to resolve, exactly as it appears in snapshot and window bodies. schema: example: urn:via:action:8dac0698-b005-4572-9801-7be144c545a5 type: string - $ref: '#/components/parameters/ApiVersion' responses: '200': description: 'Returns the resolved action: identity, version and definition.' content: application/json: schema: $ref: '#/components/schemas/IntelligenceActionEntity' '400': description: 'Invalid query parameters: `orgDid` or `urn` missing.' content: application/json: schema: type: object properties: statusCode: type: number example: 400 message: type: string example: urn must be a string error: type: string example: Bad Request '404': description: >- sharing_not_enabled: the organization does not exist or does not share with you; or action_not_found: no such action URN within that organization. content: application/json: schema: type: object properties: statusCode: type: number example: 404 message: type: string example: 'action_not_found: no such action within this organization' error: type: string example: Not Found components: parameters: ApiVersion: name: API-Version in: header required: false schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-10-16' description: >- Pin request, response, and webhook shapes to a specific dated API version (YYYY-MM-DD). Omit to use the version pinned to your API key (set when the key is created; new keys default to the latest version). New integrations should target the latest version. schemas: IntelligenceActionEntity: type: object properties: orgDid: type: string description: Organization whose action this is. example: did:web:org-a.example urn: type: string description: The resolved action version URN, echoed back. example: urn:via:action:8dac0698-b005-4572-9801-7be144c545a5 name: type: string description: Human name of the action. example: Book a train ticket description: type: - string - 'null' description: Human description of what the action permits. example: >- Books a train ticket on the person's account, within the fare they set. version: type: number description: >- Version number this URN pins. Each version is immutable once published. example: 3 published: type: boolean description: >- Whether this version was published (mandates can only pin published versions). example: true deleted: type: boolean description: >- Whether the organization has since deleted the action. Deleted actions still resolve: a URN surfaced by a snapshot was in force on live mandates. example: false digestSRI: type: - string - 'null' description: Subresource integrity digest of the definition. example: sha256-… createdAt: type: string description: When this version was created. example: '2026-06-01T12:00:00.000Z' definition: type: - object - 'null' description: >- The definition itself: `target` (method, domain, path), `userParams` and `executionParams` (declared fields with descriptions), `rules` (the policy, evaluated on every verification) and `mapper`. additionalProperties: true example: target: method: POST domain: api.rail.example path: /bookings userParams: maxFare: type: number description: Highest fare the person allows. executionParams: fare: type: number description: The fare of this booking. rules: - name: fare_cap expression: executionParams.fare <= userParams.maxFare required: - orgDid - urn - name - description - version - published - deleted - digestSRI - createdAt - definition ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.