User-authorized access
The account holder connects their own account and grants access. Permissions are scoped and revocable.
Sophtron Access & Action APIBuild agents that
Build agents that
get things done.
Turn account data into completed tasks. Retrieve the details behind bills, purchases and benefits—then let your users authorize the next step, all through Sophtron’s Access & Action API.
Built for personal AI agents and the products behind them.
From instruction to completionIllustrative
RequestPlanUser approvalExecute
YOUR USER MAKES THE FINAL CALL
Pay the electricity bill?
- Payment amount
- $142.18
- From account
- Checking ··4821
- Maximum allowed
- $250.00
DenyAllow
Illustrative approval step. No payment is initiated on this page.The agent cannot approve on the user’s behalf
Read + actAccount context and supported actions together
Plain languageDescribe the task your user wants completed
User approvalBefore critical or irreversible steps
The short answer
What is an action API for AI agents?
An action API lets an application request a task inside a connected account, rather than only retrieve data. Sophtron’s Access & Action API combines account information with free-form task instructions and approval controls, so an agent can help a user move from understanding a situation to completing an authorized action.
More value in your own product
Help users finish the job.
Give your application useful capabilities across external accounts. Start with practical tasks, and expand to higher-impact actions where the connection supports them.
| User need | Read the context | Supported action to evaluate |
|---|---|---|
| Organize account records | Available statements and billing periods | Download a statement or requested document. |
| Keep contact details current | Existing account contact information | Update the user’s contact details. |
| Stay on top of a bill | Amount due and payment deadline | Set a bill alert or update autopay preferences. |
| Resolve a questionable charge | Transaction and account information | Submit a dispute with the user’s authorization. |
| Pay an upcoming expense | Current bill and funding account | Pay the bill after explicit approval. |
Actions are institution-dependent. Changes to payments, autopay, account details and disputes should use the approval controls appropriate to their impact.
Developer workflowDescribe the outcome.
Describe the outcome.
Control the commitment.
Actions extend Sophtron’s existing Customers, Members and Accounts interface. Use a linked account ID, an instruction and guardrails for the task.
Example request body and route from Sophtron’s published action reference. Use your existing v2 authentication and an API key with the action scope.
View the complete API referenceAction request · documented example
POST /api/v2/Customers/{customerID}/Members/{memberID}/actions
{
"AccountID": "your_linked_account_id",
"Instruction": "Pay the current electricity bill in full",
"Parameters": { "MaxAmount": 250.00 },
"Mode": "execute",
"RequireApproval": "auto"
}A controlled execution flow
The user stays in charge.
Approval is part of execution, rather than a promise left to the model. Sophtron’s published action flow pauses irreversible steps for the account holder.
Connect and confirm capabilities
Link the user’s institution, complete required MFA and check whether the connection supports actions.
Submit the instruction and constraints
Describe the task and set parameters such as a maximum amount. The engine plans the steps.
Pause for the account holder
Irreversible steps enter awaiting_approval. The user allows or denies the request. An expired approval is treated as denied.
Retrieve the result
Use action status and completion information to show the user what happened. Do not report success before the task is completed.
Built for personal accounts
Permission is part of the product.
Account access carries responsibility. Keep the user involved where it matters, with boundaries around credentials and actions.
Credentials outside the model
Sophtron keeps account credentials isolated from its language models. Use the connection flow for sign-in and MFA.
Approval before commitment
Critical or irreversible actions require the account holder’s explicit decision. The agent cannot approve for the user.
Questions, answered
What developers want to know.
How is the Action API different from read-only financial aggregation?
Read-only aggregation supplies account information. The Action API extends the workflow with user-authorized tasks, such as downloading a statement, updating details or paying a bill on supported connections. The same account context helps the application determine what to propose.
Do I need to describe every browser click?
No. The action interface accepts an Instruction in plain language, along with optional structured parameters. Your application specifies the intended task and constraints; Sophtron plans the website steps.
Can the AI agent approve its own payment?
No. Sophtron’s published flow requires the account holder’s decision before irreversible steps. Agents cannot self-approve, and an expired approval is treated as denied.
Can an action be cancelled?
The action reference supports cancellation while an action is queued, planning or awaiting approval. An action that has already passed an irreversible step cannot be assumed cancellable or reversible.
Does every connected institution support write actions?
No. Check the capabilities returned for the linked member and validate the requested task. Account connectivity does not mean every possible action is available at every institution.
Why use this in a fintech product?
It lets a product extend from analysis into tasks users would otherwise complete elsewhere. For example, a bill-management product can combine bill details, reminders and an approved payment workflow inside its own customer experience.
Turn “here’s what to do” into done.
Build a product that helps users understand their accounts—and act on what matters.