MyAi for Oracle Fusion, home
Get started
How it works

Claude asks. MyAi checks. Oracle answers — as you.

Your own Claude is the assistant. MyAi supplies it with verified, read-only tools that query your company's Fusion pod as the signed-in person. Nothing runs on a shared account, and nothing is guessed.

For each person

  1. Add MyAi to Claude

    In Claude, open Settings → Connectors → Add custom connector and enter https://mcp.testingthetestingapp.online/mcp. Claude registers itself; there is no client ID or secret to type.

  2. Say who you work for

    A MyAi page opens. Enter your work e-mail (or the organisation code your administrator gave you) and check the organisation shown.

  3. Link Oracle

    Sign in on your organisation's usual Oracle page. MyAi receives a token for you from your own identity domain and verifies it against your identity domain's keys. You're returned to Claude.

  4. Ask in plain language

    Claude picks MyAi's tools, which resolve names to Oracle's exact values, check every field against your pod, and read only what you're allowed to see. Answers from a Preview module state their source and ask you to confirm.

To disconnect, remove the connector in Claude. Your Oracle session in MyAi ends as soon as Claude revokes its token; otherwise the link lapses after at most 30 days without use, or sooner if your identity domain ends the Oracle session.

For your administrator (once)

  1. Enter your pod URL

    At console.testingthetestingapp.online/onboard, enter the company name, your work e-mail and your Fusion pod URL.

  2. Automatic discovery

    MyAi follows your pod's public sign-in redirect to find your identity domain and reads its published OpenID configuration. No credentials are sent.

  3. Confirm your e-mail

    MyAi e-mails you a single-use confirmation link. Nothing is saved until you confirm.

  4. Create one identity-domain application

    The single manual step: a confidential application from a checklist MyAi pre-fills for you (redirect URL, scope, grant types). Paste its client ID and secret back into the form. See the checklist.

  5. Choose a plan and check out

    Pick a plan and the number of users. Your 14-day trial starts when the organisation is created.

The first time an administrator links Oracle from Claude, MyAi finishes the setup from the verified sign-in and runs a smoke check.

No Claude plan? MyAi Web

People without a Claude plan can use MyAi in the browser at app.testingthetestingapp.online: the same verified, read-only tools and the same Oracle sign-in, answered by Claude through your organisation's own Anthropic API key. An administrator enables it once in the admin console by pasting the key, choosing a model and setting a monthly budget. Anthropic bills the model usage to your organisation directly; each person uses the same MyAi seat either way. How to enable MyAi Web

Inside every answer

Verified, not guessed

Checked against your pod

Before a query leaves, MyAi checks every resource and field against your pod's own API description, for exactly how it is used. A query that doesn't pass is never sent.

Names resolved, not assumed

Suppliers, customers, business units and coded values are matched to Oracle's exact registered names and lookups before anything is filtered on them.

Honest about gaps

Some data isn't in Oracle's REST API — bank statements, reconciliations, full trial balances. MyAi says so plainly and names the Oracle report that answers it. Your organisation can also add its own reports.

Oracle's standard (“seeded”) reports run through Oracle's own scheduler as the signed-in person, so Oracle's data security applies. They are being enabled report by report after each is captured and checked; until then, MyAi tells you which Oracle report to run.

Static egress IPs for your allowlists

Many Fusion customers restrict their pod and identity domain to known source addresses. Every call MyAi makes to Oracle — REST queries, report jobs, token exchanges and release checks — leaves from the same small set of static IP addresses.

  • You allowlist all of them on your pod and identity domain. The onboarding checklist shows them.
  • They don't change with deployments. If we ever need to add one, we tell you before it is used.
  • Inbound, you open nothing: MyAi never receives connections from your pod.

Each hosting region has its own addresses. Regions and data residency

Oracle's quarterly updates, handled

Oracle updates Fusion every quarter. MyAi checks each organisation's pod daily for a new release or patch, compares Oracle's API before and after, and re-runs its verification against both:

  • Additive changes (new resources, fields or finders) are applied automatically once every verified query still passes.
  • Anything that could change an answer — a removed or tightened field MyAi relies on — is held for review by the MyAi team, never applied silently.
  • The check reads only metadata, as an administrator who explicitly opted in when linking Oracle. There is no service account.

Ready when your Oracle team is

Start onboarding with your pod URL, or read the administrator checklist first.

Get started Administrator setup