x402 content artifacts textus.dev/support

Support · Europe/Berlin

Bring evidence, never secrets.

Support covers delivery verification, ambiguous-settlement reconciliation, malformed artifacts, duplicate settlement, licence clarification, and refund review.

Initial response target: five business days in Europe/Berlin.

Include

  • Exact resource URL
  • Canonical Textus resource ID (or historical storyId)
  • Selected SKU or productKind
  • Approximate UTC timestamp
  • X-Textus-Receipt (or identical legacy X-Story-Receipt)
  • Transaction or settlement reference
  • Public paying-wallet address
  • Expected delivery revision and digest
  • Source-master revision and digest, when present
  • For historical purchases: original SKU and receipt-bound format
  • HTTP status and X-Request-ID

Never include

  • PAYMENT-SIGNATURE
  • Seed phrase or private key
  • Wallet recovery material
  • Unredacted credentials or tokens

Lost response?

First replay the exact same request and identical signature. A settled receipt can recover the immutable bytes.

Integration question?

Start with the quickstart, OpenAPI, and content artifact schema. Baseline direction is editable production material; voice selection and rendering remain buyer-controlled.

Licence or refund?

Read the human terms and cite the contract version and artifact revision in your message.