# Bitpont Agent Recovery | Retries, Receipts and Partial Data

Handle schema errors, access restrictions, stale quotes, partial provider reads and uncertain wallet or bridge outcomes.

Canonical: https://www.bitpont.com/developers/agent-recovery/


## Correct a request before sending it

Call bitpont_describeTool for the exact schema and bitpont_checkInputs with the tool name and arguments. A failed check returns JSON Pointer paths, such as /payments/0/amount. This checks field shape and precision rules declared in the schema. Live eligibility, balance and execution simulation occur at the provider step.

Server-side JavaScript
```
import {BitpontClient} from './bitpont-client.mjs';
const client = new BitpontClient({publicAccess:true});
const result = await client.agent('checkInputs', {
  tool: 'convertAmount',
  arguments: {chainId:'evm:1', unit:'display', value:'1.25'}
});
// The address field is missing. No provider was contacted.
console.log(result.data.issues);
```

## Handle access, rate and provider errors

- 401 or 403. Check whether the tool needs a partner key and which scope it requires. Wallet signatures authorize a separate step.
- 429. Honor Retry-After. Batch and market-view calls consume one unit per underlying read. Request higher limits at [support@bitpont.com](mailto:support@bitpont.com).
- 409 on a quote. Refresh the quote with the same network, token identities and owner. Review fees and expiry again.
- Partial read. Keep successful rows, store each resource cursor, and retry the unavailable resource with its original parameters.

## Recover an uncertain outcome

Keep the network, account, request ID, quote or order ID and source transaction hash. After a timeout, inspect the recorded identity first. An included EVM transaction can still need a protocol-specific event. A bridge needs destination delivery, a perpetual order needs a fill, and a Safe payment needs the matching finalized execution and delivery evidence.

## Read the same swap receipt as Portfolio

For a Jupiter swap or fee-bearing KyberSwap, call POST /api/v1/agent/execution/swap-receipt with the original private workspace and executionId. With MCP, call bitpont_swapReceipt. Both use the same receipt data shown in [Portfolio Activity](/portfolio/activity/#portfolioSwapReceipt). A finalized transaction, an attributable wallet output and a verified Bitpont fee are three separate observations.

Receipt fieldHow to read it

state, transactionId, blockCheck the transaction identity and finality. Refresh the same execution while pending or after an unavailable response.

actualOutput, walletDelta, deltaSourceAmounts are base-unit strings for the identified asset. ERC-20 wallet transfer events report a net transfer. Native currency balance changes can also include gas or rent. Leave an unattributable output unknown.

fee.quotedAmount, fee.receivedAmountUse the quoted amount for review. Use the received amount for reconciliation when fee.state is verified. Keep the token and beneficiary with the amount.

```
const result = await client.agent("swapReceipt", {executionId});
const receipt = result.data;
console.log(receipt.transactionId, receipt.actualOutput, receipt.fee);
```
Restore the original workspace when constructing client. [Read the swap settlement walkthrough](/help/ai-agents/verified-swap-receipts/).

## Prepare a support report

Include the tool name, request ID, approximate UTC time, HTTP status and observed stage. Exclude API keys, wallet credentials and signatures. The [Business integration brief](/business/#partner-start) helps size a recurring workload.

## Reconcile workspace activity over a month

Request POST /api/v1/agent/business/report with a UTC month and the original workspace. Retain the next page cursor and reconcile each execution against the wallet, network, asset and transaction identifiers. POST /api/v1/agent/business/events supports replay from a saved event cursor. Save that cursor after the downstream system has processed the event. Keep quoted, claimable and verified fees distinct from wallet-authorized referral payables.

[Open Business settlements](/business/#settlements) · [Read the integration and delivery guide](/help/ai-agents/reconcile-settlements/)

## Find the next task that needs attention

Use taskOverview to count recorded tasks by state, kind and destination network in the original workspace. Use taskInbox with the same filters, supplying nextCursor as before for the next page. Refresh the selected task with taskStatus before deciding whether to prepare the current step.

[Recover unfinished financial tasks](/help/ai-agents/resume-workspace-task-inbox/)

## Investigate a specific settlement exception

Use businessFindReceipt with the exact execution ID, source transaction or payment transaction. Page through businessReceiptHistory with after to review the evidence already observed. Use businessExceptions for an outstanding category in a UTC month and businessFeeTotals for token-level sums. Inspect unidentifiedRows and conflictingGroups before closing the period.

[Investigate missing output or affiliate fee evidence](/help/ai-agents/investigate-settlement-exceptions/) · [Business settlements](/business/#settlements)


