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

# June 2026 update

> ARGOS Omni product update for June 2026

Hello from ARGOS Omni.

Here is what shipped in June.

***

## The Credit Usage screen

<span style={{backgroundColor: '#EEF4FF', color: '#0064FF', padding: '4px 12px', borderRadius: '16px', fontSize: '13px', fontWeight: '600'}}>New Feature</span>

You can now see where your credits went, directly in the dashboard. **Project Management** gained a [Credit Usage](/en/omni/dashboard/project/credit-usage) tab.

<Frame caption="The Credit Usage tab — four summary cards and the transaction table.">
  <img src="https://mintcdn.com/argosidentity/OPYUfjaSdQpOBnpM/images/omni/en/project-credit-usage.png?fit=max&auto=format&n=OPYUfjaSdQpOBnpM&q=85&s=3b1ca558f7766fc6afc141bdeb04bba1" alt="Credit Usage tab" width="3736" height="1977" data-path="images/omni/en/project-credit-usage.png" />
</Frame>

| Area          | Contents                                                                   |
| ------------- | -------------------------------------------------------------------------- |
| Period        | Presets for the last 7, 14, 30, and 90 days, plus a custom range           |
| Summary cards | Total, and the three categories Environment · Operation · Tools            |
| Transactions  | Per-transaction history. Search by TXID or resource ID, filter by category |
| Export CSV    | Save the current period to a file                                          |

The transactions gained **BASE** (the base rate) and **Quantity** columns, so you can work out how a final credit figure was reached, row by row. One analysis is recorded across several rows — the analysis run itself is one Operation row, and each engine it called is one Tools row.

Which actions deduct credits is covered in [how credits are charged](/en/omni/dashboard/project/credit-pricing).

***

## Address Validation engine

<span style={{backgroundColor: '#EEF4FF', color: '#0064FF', padding: '4px 12px', borderRadius: '16px', fontSize: '13px', fontWeight: '600'}}>New Feature</span>

The **Address Validation** engine was added. It verifies that a postal address on a document exists, and normalizes it.

Put a clause such as "validate that the registered address is a real address" in your policy and it is assigned automatically. It supports **40 regions** (ISO 3166-1 alpha-2) — [AI model and engines](/en/omni/dashboard/workflow-setup/engine-selection#engine-catalog).

<Note>
  Korea is not among the 40 regions Address Validation supports. The call fails when the target country does not match, so state which country the verification subject is in when you write the policy.
</Note>

***

## Clearer progress while a workflow is created

<span style={{backgroundColor: '#F0FDF4', color: '#16A34A', padding: '4px 12px', borderRadius: '16px', fontSize: '13px', fontWeight: '600'}}>UX Improvement</span>

Playbook generation takes 2–3 minutes. We fixed the screen not showing clearly how far along it was. The period picker calendar now follows the interface language too.

***

## Related pages

* [Credit usage](/en/omni/dashboard/project/credit-usage) · [How credits are charged](/en/omni/dashboard/project/credit-pricing)
* [AI model and engines](/en/omni/dashboard/workflow-setup/engine-selection)