> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loqate.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IBM watsonx Orchestrate Agent

> Reach as a native watsonx Orchestrate (WXO) agent — a data-quality agent that verifies and cleanses address, email, and phone data from inside WXO chats, collaborations, and workflows.

<Note>
  **Coming soon.** The Reach agent for IBM watsonx Orchestrate is not yet generally available. This documentation describes the agent ahead of its launch — features and steps may change before release.
</Note>

**GBG Reach** is available as a native [IBM watsonx Orchestrate](https://www.ibm.com/products/watsonx-orchestrate) (WXO) agent. It brings the Reach verification engine — addresses, emails, and phone numbers with policy-aware decisioning — directly into watsonx Orchestrate.

<Note>
  This is the same Reach product documented elsewhere in this section. The difference is the delivery surface: instead of the `lqt` CLI or a standalone MCP server, verification runs as a first-class WXO agent that you discover and add from inside watsonx Orchestrate — no code or local install required.
</Note>

## How it relates to Reach

The WXO agent is powered by the same hosted Reach engine that drives the [MCP server](/ai-agents/mcp/overview). The policy logic, confidence scoring, and AVC codes all run server-side, so a verification in watsonx Orchestrate returns the same result as the equivalent CLI or MCP call. You interact with it entirely through watsonx Orchestrate — in chat, as a collaborator, or as a step in a workflow.

## Capabilities

<CardGroup cols={2}>
  <Card title="Address Verification" icon="location-dot">
    Verify, standardise, and cleanse postal addresses from free-form text or structured fields.
  </Card>

  <Card title="Email Validation" icon="envelope">
    Check deliverability and format, with disposable-domain and risk detection.
  </Card>

  <Card title="Phone Validation" icon="phone">
    Validate and format phone numbers, E.164 preferred with country-code fallback.
  </Card>

  <Card title="Combined Contact" icon="shield-check">
    Verify address, email, and phone together with an overall accept / review / reject recommendation.
  </Card>

  <Card title="Document Upload" icon="file-csv">
    Paste a block of records or upload a CSV directly in the watsonx Orchestrate chat.
  </Card>

  <Card title="Policy Decisioning" icon="shield-halved">
    Built-in `strict`, `shipping`, `standard`, and `permissive` policies control accept / review / reject thresholds.
  </Card>
</CardGroup>

## Structured output

Every verification returns a structured report that collaborator agents and workflows can act on without human interpretation:

```json theme={null}
{
  "summary": "Verified 1 record: Jane Doe accepted",
  "results": [
    {
      "type": "contact",
      "name": "Jane Doe",
      "address": "1600 Amphitheatre Parkway, Mountain View, CA 94043, USA",
      "email": "jane.doe@example.com",
      "phone": "+16502530000",
      "decision": "accept",
      "confidence": 0.95,
      "policy": "standard",
      "reason": "All fields verified and standardised"
    }
  ]
}
```

## What you need

* Access to an **IBM watsonx Orchestrate** instance
* A **Loqate subscription**, provisioned and purchased through watsonx Orchestrate. Your Loqate API key is issued as part of that process — you don't need a separate Loqate account.

## Next steps

<CardGroup cols={2}>
  <Card title="Usage" icon="comments" href="/ai-agents/wxo/usage">
    Discover and add the agent, then use it in chat, as a collaborator, or in a workflow.
  </Card>

  <Card title="Policies" icon="shield-halved" href="/ai-agents/reference/policies">
    Built-in and custom decisioning policies.
  </Card>
</CardGroup>