ATUM on MERX: Passport Connection and Agent Permissions

ATUM helps a person link a passport to a service and give a software agent explicit, reviewable permission to use that service. MERX integrates ATUM so the person who owns a MERX account can keep the account link, the agent's access, and the limits on that access clear and separate.

The key idea is simple: linking a passport to a MERX account is not the same as authorizing an agent to act.

Why MERX uses ATUM

An agent can be useful for recurring research or operational work, but it should not inherit open-ended access just because it belongs to an account owner. ATUM gives the owner a place to review a requested permission before it is granted.

That makes the relationship easier to understand: MERX is the service, the passport links to the MERX account, and the owner decides whether an agent receives access. The owner can review the limits of that access and revoke the permission in ATUM.

Passport link and agent permission are separate

The passport link connects an existing ATUM passport with the current MERX account. It does not place an order, debit a balance, or approve a developer agent.

Agent permission is a separate choice in ATUM. The owner reviews the service request and its limits, then explicitly approves the agent when it is appropriate. The same permission can later be reviewed or revoked.

This separation matters when an account has more than one tool or agent. A passport link gives the owner a consistent starting point; every agent still needs its own clear permission.

What the first integration supports

The first sandbox integration supports current prices, previews, and simulations. It does not debit a balance. These tools help an owner or developer understand an action before deciding whether to allow anything further.

The MERX workspace has an ATUM page for reviewing the passport connection and opening the available owner journey. It also links to the public Node.js Device example for developers.

For developers

The Device example is a practical starting point for an agent integration. Download it from the ATUM page in the MERX workspace and follow its README. When the example requests access, review the request in ATUM before approving it.

Use the example to keep permission explicit in your own workflow: check what the agent needs, set the limits you want, and revoke access when it is no longer needed.

Tags: ATUM, MERX, passport connection, agent permissions, sandbox, Device Authorization