DOCUMENTATIONv2

POST

Smart-contract lifecycle

Analyze authority

/api/v2/contracts/{launch_uuid}/analysis

AUTHENTICATIONBearer token · contracts:readAUTHORITATIVE OWNERcontract-authority-serviceCONTRACT AUTHORITYGenerated Rust OpenAPISTATUSSource ready · production listed

PURPOSE + BUSINESS CONTEXT

Analyze contract authority, runtime policy, and deployment prerequisites.

WHEN THIS CALL IS USEFUL

Call this when a contract author, authority reviewer, deployment operator, or contract-lifecycle agent needs to apply the documented analyze authority transition after re-reading the current authoritative state so it can move a contract launch through draft, analysis, governance binding, freeze, evidence, and deployment preparation without collapsing those gates.

OUTCOME · Create or advance

What changes

Creates or advances only the analyze authority resource described by this contract after authorization, validation, policy, and idempotency gates pass.

WHY IT MATTERS

Gives people and agents a contract-backed way to advance analyze authority.
Creates an auditable path from editable launch intent to immutable, authority-bound deployment inputs.

ISOLATION + AUTHORITY

Launch owner, workspace, source artifact, analysis, declared authority, governance binding, frozen revision, deployment preparation, target network, and runtime deployment remain distinct. Analysis or preparation does not deploy code, freezing does not approve it, and no contract route grants wallet, publisher, matching, trading, or external-domain authority.

BEFORE YOU CALL

Authenticate at the documented boundary: bearer+scope.
Supply the required launch_uuid (path), request (body) exactly as defined by the live contract.
Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.
Resolve the launch owner, current revision, source and configuration commitments, authority analysis, governance binding, and target-network policy.

WHAT TO DO NEXT

Re-read analyze authority using the canonical identifier returned by this operation.
Reconcile an ambiguous response with the same idempotency key before attempting another mutation.
Compare the launch revision, source and configuration commitments, authority analysis, governance binding, and target-network policy before moving to the next contract stage.

AGENT GUIDANCE

Use analyze authority only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Supply the required launch_uuid (path), request (body) exactly as defined by the live contract.
Treat draft editing, authority analysis, governance binding, freeze, evidence completion, deployment preparation, deployment, activation, and external effects as separate states.
After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.

MACHINE CONTRACT

The exact deployed parameters, schemas, responses, security requirements, and Hybrid-Chain agent metadata are authoritative at this operation's production OpenAPI JSON Pointer. The readable tables below add integration guidance; the deployed OpenAPI controls if guidance and the machine contract ever differ.

Open the authoritative production contract ↗

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

AuthorizationheaderRequired

Bearer tokenCredential containing the contracts:read scope.EXAMPLEBearer hc_live_…

Idempotency-KeyheaderRequired

ASCII string · 1–128Caller-generated key reused for every retry of the same logical mutation.EXAMPLElaunch-treasury-v1-001

launch_uuidpathRequired

string · 1–160Contract launch UUID or canonical slug.EXAMPLE9b51ed4c9c8f4aec85d1bd5520e40557

RESPONSES

Status and payload examples

200Authoritative non-mutating authority analysis.Mutation completed · JSON RESPONSE+

{
  "analysis": {
    "score": 87,
    "grade": "A",
    "riskBand": "LOW",
    "requiredRiskAcceptances": [
      "ROLE_REUSE"
    ]
  },
  "configurationHash": "sha256:8888888888888888888888888888888888888888888888888888888888888888",
  "mutationPerformed": false
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then re-read analyze authority using the canonical identifier returned by this operation.
RETRY SAFETY: Do not repeat a successful mutation merely to confirm it. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION: Persist returned identifiers, versions, commitments, and receipts. Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.

400The request or required headers are malformed.Request must change · JSON RESPONSE+

{
  "code": "invalid_json",
  "message": "The request or required headers are malformed."
}

INTEGRATION DECISIONinvalid_json

CALLER ACTION: Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY: Do not retry the same invalid request. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION: Compare the submitted values with the documented constraints before another call. Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

401The bearer credential is missing or invalid.Authentication required · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "The bearer credential is missing or invalid."
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Discard the rejected credential, complete the documented authentication or reassertion flow, and rebuild any request signature with fresh timestamps and nonces.
RETRY SAFETY: Retry only with a newly valid credential and fresh replay-protection values. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION: Assume the outcome is unknown only when the connection failed after transmission; otherwise authentication failed before domain work. Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

403The credential lacks the required contract scope.Authority or policy denied · JSON RESPONSE+

{
  "code": "insufficient_scope",
  "message": "The credential lacks the required contract scope."
}

INTEGRATION DECISIONinsufficient_scope

CALLER ACTION: Verify the exact scope, tenant or workspace membership, owner boundary, step-up purpose, feature policy, and resource eligibility. Never broaden authority automatically.
RETRY SAFETY: Do not retry until the missing authority or policy condition has been deliberately resolved with least privilege.
STATE RECONCILIATION: Confirm the caller and resource resolve to the same authority boundary for workspace governance proposals, approvals, signing handoffs, policy versions, and execution evidence.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

404The requested launch does not exist in the caller's workspace.Resource not visible · JSON RESPONSE+

{
  "code": "contract_not_found",
  "message": "The requested launch does not exist in the caller's workspace."
}

INTEGRATION DECISIONcontract_not_found

CALLER ACTION: Verify the canonical identifier and authenticated owner boundary. A 404 may intentionally conceal a resource outside the caller's authority.
RETRY SAFETY: Do not retry the unchanged identifier repeatedly. Refresh the relevant collection or lookup before choosing another identifier.
STATE RECONCILIATION: Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

409The request conflicts with immutable launch state or existing governance evidence.State reconciliation required · JSON RESPONSE+

{
  "code": "contract_conflict",
  "message": "The request conflicts with immutable launch state or existing governance evidence."
}

INTEGRATION DECISIONcontract_conflict

CALLER ACTION: Stop the mutation sequence and fetch the latest authoritative resource, lifecycle state, version, ETag, reservation, or existing idempotency result.
RETRY SAFETY: Retry only after reconciling the conflict. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION: Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

422The canonical contract request failed validation.Request must change · JSON RESPONSE+

{
  "code": "invalid_request",
  "message": "The canonical contract request failed validation."
}

INTEGRATION DECISIONinvalid_request

CALLER ACTION: Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY: Do not retry the same invalid request. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions.
STATE RECONCILIATION: Compare the submitted values with the documented constraints before another call. Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

503The authoritative contract registry is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "contract_registry_unavailable",
  "message": "The authoritative contract registry is unavailable."
}

INTEGRATION DECISIONcontract_registry_unavailable

CALLER ACTION: Preserve the exact request and treat the outcome as uncertain until authoritative state proves whether it committed.
RETRY SAFETY: Reconcile before retrying. For one logical mutation, retain the same Idempotency-Key and byte-equivalent request. Never reuse that key for changed instructions. Use bounded backoff with jitter.
STATE RECONCILIATION: Refresh the proposal, approval threshold, signer set, policy version, and execution or rejection receipt before changing or resubmitting governance instructions.
ESCALATE WHEN: Escalate when signer eligibility, threshold evidence, proposal version, or downstream execution state remains inconsistent after a fresh governance read.

OPERATIONAL NOTES

Security and lifecycle guarantees

The endpoint accepts no scoring inputs; the authoritative service computes the result from the retained draft and current wallet epochs.

DOCUMENTATION STATUS

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-09-11T06:35:11.572Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation ↗Return to the V2 directory ↗