Skip to content
veycera

Connections

The systems that supply evidence. Access and freshness are separate from outcome verdicts.

No verification run recorded. Each source shows its own available read history.

Coverage and freshness

Zendesk

Read-only

environment prod_yc-recording-v1 · tenant yc-recording-v1

Connected

Latest retained source read:

Setup guide

To use your Zendesk account, configure read-only credentials in the deployment environment.

  1. Create a read-only OAuth credential

    Create a Zendesk OAuth client and obtain a token with tickets:read access. Use an agent account that can read the tickets you want to monitor.

  2. Add the server credentials

    Set your Zendesk subdomain and OAuth token in the deployment environment.

    ZENDESK_SUBDOMAIN=your-subdomain
ZENDESK_OAUTH_TOKEN=your-access-token

  3. Identify the monitored agents

    Enter the Zendesk user IDs that author the agent’s ticket comments. Separate multiple IDs with commas.

    ZENDESK_AI_AGENT_USER_IDS=12345,67890

  4. Redeploy and read the records

    Redeploy the live environment, then select Run outcome checks. Review the recorded result and any source access errors.

    View outcomes →

Official documentation

Access and configuration details

Demo connection · example records

Simulated access check

Zendesk / Gorgias: read scopes granted, write scopes absent. Recorded Demo time · Oct 30, 16:16 UTC. This checks the demo access model.

Records read

  • Tickets: id, status, category, requester, order reference, agent approval, requested amount and currency, resolution message, timestamps
  • Ticket comments by the monitored agent's user ids (for claim extraction)
  • Nothing is written; no customer PII beyond the ticket is stored

Permission scopes

  • tickets:read · granted
  • tickets:write · absent
Credential reference and rotation

Rotate the read-only credential in the server environment using ZENDESK_OAUTH_TOKEN, then redeploy. Never paste a token into this page.

Stripe

Read-only

environment prod_yc-recording-v1 · tenant yc-recording-v1

Connected

Latest retained source read:

Setup guide

To read your Stripe account, use a restricted API key with read-only permissions.

  1. Create a restricted key

    In Stripe Dashboard, open API keys and create a restricted key. Grant Read access to Charges, PaymentIntents and Refunds; leave write permissions disabled. Start with a sandbox key.

  2. Add the server key

    Store the restricted key in the deployment environment. Use the key for the sandbox or live account whose records you want to read.

    STRIPE_RESTRICTED_KEY=rk_test_...

  3. Set the order reference field

    Enter the Stripe metadata key that contains your order ID. The default is order_id.

    STRIPE_ORDER_METADATA_KEY=order_id

  4. Redeploy and read the records

    Redeploy the live environment, then select Run outcome checks. Review the payment evidence and any source access errors.

    View outcomes →

Official documentation

Access and configuration details

Demo connection · example records

Simulated access check

Stripe: read scopes granted, write scopes absent. Recorded Demo time · Oct 30, 16:16 UTC. This checks the demo access model.

Records read

  • Charges and payment intents: id, amount, currency, status, created, metadata order id
  • Refunds: id, amount, currency, status, created, reason
  • Never creates refunds, charges or payments; write scopes are refused at registration

Permission scopes

  • charges:read · granted
  • refunds:read · granted
  • refunds:write · absent
  • charges:write · absent
Credential reference and rotation

Rotate the read-only credential in the server environment using STRIPE_RESTRICTED_KEY, then redeploy. Never paste a token into this page.

GitHub

Read-only

example/support-agent · main

Connected

Latest retained source read: Not recorded

Setup guide

The demo includes a prepared example repository with revision history and configuration. Connecting a live GitHub repository is not available on this page.

  1. Open the repository details

    Expand Access and configuration details on this card to view the bundled example/support-agent repository.

  2. Review the revision history

    Read the four prepared revisions in order to see the retry-limit and amount-unit changes. Demo revision labels identify the examples; they are not Git commit hashes.

  3. Inspect the latest configuration

    Open the latest agent.config.json to review the configuration after those changes. These bundled records are available without GitHub credentials.

Official documentation

Access and configuration details

Demo connection · example records

Repository access

Read-only access to the included example snapshot. Live GitHub access is not configured.

Records read

  • Repository name, branch and tracked configuration file
  • Four example revisions with commit messages and configuration snapshots
  • Read-only repository records supplied with the demo

Repository snapshot

example/support-agent · branch main · file agent.config.json

  1. Initial refund agent configurationAmount unit: cents · retry limit: 2
  2. Raise provider retry limit to 3Amount unit: cents · retry limit: 3
  3. Refactor amount handling to use display unitsAmount unit: dollars · retry limit: 3
  4. Restore retry limit after load testAmount unit: dollars · retry limit: 2
Latest agent configuration
{
  "amountUnit": "dollars",
  "paymentLookup": "by_order_id",
  "treatPendingAsSuccess": false,
  "confirmBeforeClaim": true,
  "idempotencyKey": "per_request",
  "closeTicketBeforeConfirm": false,
  "maxRetries": 2
}

Orders

Read-only

environment prod_yc-recording-v1 · tenant yc-recording-v1

Connected

Latest retained source read:

Setup guide

The included order source is ready to use. It models a Shopify-style store; live store onboarding is not available on this page.

  1. Open an outcome

    Choose a cancellation or refund outcome that references an order.

    View outcomes →

  2. Inspect its order evidence

    Select Evidence and find the Order record. Check its status, total, source and recorded timestamp.

  3. Check how the order was matched

    Review the correlated identifiers. The ticket’s explicit order reference determines which order is checked.

Official documentation

Access and configuration details

Demo connection · example records

Simulated access check

Order management (Shopify-style): read scopes granted, write scopes absent. Recorded Demo time · Oct 30, 16:16 UTC. This checks the demo access model.

Records read

  • Orders: id, customer, status, total, currency, timestamps
  • Customer lookup by id or email, only to list that customer's own orders

Permission scopes

  • orders:read · granted
  • customers:read · granted
  • orders:write · absent

Demo model: Order management (Shopify-style)

Fulfillment

Read-only

environment prod_yc-recording-v1 · tenant yc-recording-v1

Connected

Latest retained source read:

Setup guide

The included shipment source is ready to use. Live carrier onboarding is not available on this page.

  1. Open a cancellation outcome

    Choose an outcome with a shipment linked to the requested order.

    View outcomes →

  2. Inspect the shipment evidence

    Select Evidence and find the Shipment record. Review its status, dispatch time and the recorded source.

  3. Compare the required state

    Review the shipment check beside the observed record. A resolved support ticket alone does not show that the shipment stopped.

Official documentation

Access and configuration details

Demo connection · example records

Simulated access check

Fulfillment / carrier API: read scopes granted, write scopes absent. Recorded Demo time · Oct 30, 16:16 UTC. This checks the demo access model.

Records read

  • Shipments: id, order, status, dispatch time, timestamps

Permission scopes

  • shipments:read · granted
  • shipments:cancel · absent

Demo model: Fulfillment / carrier API

About connection setup

Open a source's Setup guide for numbered steps and official documentation. Zendesk and Stripe support server-side credentials. Orders, Fulfillment and GitHub use prepared example records in this demo.