2AYE

A bounded engagement. An observable result.

Start your AI security evaluation.

Inspect the authority boundary, try the public scenarios and choose one agent action to evaluate against policy, human review and execution evidence.

BEFORE AN ENGAGEMENT BEGINS

Know what you will evaluate.

Use these items to agree a statement of work. Deliverables, access, timing and price are confirmed during scoping.

Bring one workflow

  • Name its owner, agent, exact action and protected system.
  • Identify a test environment, permitted test data and the receiver owner.
  • Confirm source access and identity or device participation where needed.

Agree the evidence

  • A scoped integration and responsibility map.
  • Observed permitted and refused actions, with applicable replay, expiry and recovery checks.
  • A review of destination evidence, unresolved outcomes and the next-stage decision.

Set commercial boundaries

  • Agree integration effort, environment, support and evidence handling.
  • Confirm the pricing basis and exclusions in the statement of work.
  • Live payments, managed key custody, physical-device acceptance and independent validation need separate scope.

A request does not provision a trial, guarantee a delivery date or establish production availability.

Start exploring now

Try illustrative prompt-injection, parameter-change and replay scenarios, then request verification material by email under an agreed NDA. These establish their stated reference scope; they do not test your own agent or production receiver.

Choose a workflow

Start with one action. These choices describe evaluation interests across identity, agents, commerce and integrations; they do not assert that every connector or payment flow is available.

Agree what success means

  1. 1. Define scope

    Name the owner, agent or identity, exact action, protected resource, integration and environment.

  2. 2. Agree acceptance

    Specify a legitimate success, changed-parameter refusal, cross-tenant refusal, expiry, replay and recovery checks relevant to the workflow.

  3. 3. Record responsibilities

    Agree access, test data, receiver ownership, human/device participation, commercial terms and evidence handling.

  4. 4. Review the evidence

    Separate authorization from actual execution. Identify provider or independent receiver evidence, unresolved outcomes and the decision on the next stage.

Payment capture, live credential custody, physical-device acceptance and independent receiver validation retain their own release gates. An evaluation is not a certification or a promise of production availability.