Coinsenda LATAM 🌎

Showing 25 of 82 from the live probe.

• Coinsenda Flow Getaccounts

  [Flow:account] Get all accounts for the authenticated user. Returns an array of account objects. A newly onboarded user may have system-created default accounts or an empty array. Source: account-service / user / __get__accounts (native hasMany) Access: user (level_0) Response model (from openapi-specs/account.json): - id: ObjectID - userId: ObjectID - name: string - currency: string (e.g. 'bitcoin', 'cop', 'usdt') - currency_type: string ('crypto' | 'fiat') - available: object (BigNumber) - res

• Coinsenda Flow Addnewaccount

  [Flow:account] Create a ledger Account for the authenticated user. Onboarding does not create Accounts. Call this before depositing or swapping a currency the user does not already hold. A second trade Account for the same currency fails with 465 (account_13, alreadyHaveOne). The currency must be enabled and visible. userId is taken from the JWT; country is injected by the SDK. Source: account-service / account / addNewAccount Access: user (level_0)

• Coinsenda Flow Generatekeypair

  [Flow:auth] Generate an RSA 2048-bit key pair for signature-based authentication. Local operation (no HTTP). Exposed as Flow/Tool because the MCP agent needs to generate keys for the user.

• Coinsenda Flow Savetokeystore

  [Flow:auth] Save an identity to the local keystore for later use with authenticateAs. Local operation (no HTTP, no client). The keystore persists RSA keys so the MCP agent can authenticate without passwords.

• Coinsenda Flow Authenticateas

  [Flow:auth] Authenticate using a saved identity from the local keystore. Reads the privateKey from keystore and authenticates via RSA signature. On success, sets the JWT on the client so subsequent requests are authenticated.

• Coinsenda Flow Pairmcpagent

  [Flow:auth] Complete MCP agent pairing flow. The user generates a pairing code in the Coinsenda app, then shares it with the MCP agent. This flow exchanges the code for a JWT, generates an RSA keypair, registers the public key, verifies pubkey login works, and saves the identity to the local keystore. Orchestrates: 1. POST /auth/pairing-otp (auth-service) — exchange code for JWT 2. Decode JWT — extract userId, email, clientId 3. Generate RSA 2048 keypair (local) 4. POST /profiles/add-api-public-

• Coinsenda Flow Finddepositaccounts

  [Flow:deposit] Find available deposit accounts (deposit methods). Returns the system-wide deposit accounts filtered by optional currency and provider type. Only returns enabled and visible accounts. This is a public endpoint -- no authentication required. IMPORTANT: Some deposit accounts have an external_identity field that indicates an external KYC verification is required before a DepositProvider can be created. The agent MUST check this field on the chosen deposit account before calling creat

• Coinsenda Flow Createdeposit

  [Flow:deposit] Create a fiat deposit. Internally handles DepositProvider reuse/creation. Orchestration flow: 1. Get user's existing DepositProviders 2. Find one matching providerType + state=accepted + enabled=true 3. If not found, create a new one via createDepositProviderByAccountIdPublic 4. Create the Deposit via addNewDepositPublic Source: deposit-service (3 endpoints chained) Access: user (level_1) The response includes metadata fields that vary by provider_type. The MCP agent MUST check th

• Coinsenda Flow Getdepositproviders

  [Flow:deposit] Get the authenticated user's deposit providers. Returns the user's existing deposit providers, optionally filtered by currency_type or provider_type. Only returns providers that are accepted and enabled. Each provider contains an `account` object with the deposit details (crypto address, bank info, etc.). Use cases: - "What is my USDT address on Tron?" -> filter providerType: 'tron' - "Show my bank deposit details" -> filter currencyType: 'fiat' - "List all my crypto addresses" ->

• Coinsenda Flow Getdeposits

  [Flow:deposit] Get the authenticated user's deposits. Returns the list of deposits for the current user (all states). Use cases: list pending/confirmed/accepted deposits, check deposit history. Source: deposit-service / user / __get__deposits (native hasMany) Access: user ($owner) Response model (array of deposit objects): - id: ObjectID - state: string (pending, confirmed, accepted, rejected, canceled) - currency: string - amount: object (BigNumber) - deposit_provider_id: ObjectID - currency_ty

• Coinsenda Flow Createdepositproviderforaccount

  [Flow:deposit] Create a deposit provider for a user account linked to a specific deposit account (e.g. Bre-B, Bancolombia, bank_usd, or any depositAccount id from findDepositAccounts). Use case: generate deposit providers for a given account and deposit method (e.g. pass depositAccount id of breb to create a Bre-B provider for that account). VARIANTS (by target deposit account provider_type): - bank (e.g. bancolombia): returns a REUSABLE provider (single_use=false, state=accepted) linked to the

• Coinsenda Flow Canceldepositproviderpublic

  [Flow:deposit] Cancel a deposit provider for the authenticated user. Cancels the DepositProvider: calls DAC to cancel the external key and marks the DP as rejected/disabled (state=canceled, enabled=false). Returns the count of records updated. Source: deposit-service / depositProvider / cancelDepositProviderPublic Access: user (level_0)

• Coinsenda Flow Blockdepositproviderpublic

  [Flow:deposit] Block a deposit provider for the authenticated user. Blocks the DepositProvider: calls DAC to suspend the key in the external provider (blockKey) and sets the DP enabled=false. Returns the count of records updated. Source: deposit-service / depositProvider / blockDepositProviderPublic Access: user (level_0)

• Coinsenda Flow Reactivatedepositprovider

  [Flow:deposit] Reactivate a blocked deposit provider for the authenticated user. Reactivates a DepositProvider that was previously blocked (enabled=false). Calls DAC to reactivate the key in the external provider and sets enabled=true. The DP must be in state=accepted and enabled=false (blocked state). Source: deposit-service / depositProvider / reactivateDepositProviderPublic Access: user (level_0)

• Coinsenda Flow Getpaymentrequests

  [Flow:deposit] Get the authenticated user's payment requests. Returns the list of PaymentRequests created by the user (cobros). Each PR has: id, amount, amount_num, currency, state, account_id, expiration_date, external_id. Source: deposit-service / user / __get__paymentRequests (native hasMany) Access: user ($owner)

• Coinsenda Flow Addnewpaymentrequest

  [Flow:deposit] Create a new payment request (cobro). The cobrador creates a PR specifying amount, currency, and expiration time. The backend auto-creates 'payment' and 'payment_hidden' type accounts for the user. Expiration minimum is 60 minutes (backend enforces this). Callback fields are optional; omit them unless the merchant needs a redirect URL and extra redirect metadata after payment finalization. AFTER CREATION: Share the returned `payment_request_url` with the payer. This URL opens the

• Coinsenda Flow Getpaymentrequestdetails

  [Flow:deposit] Get payment request details (public endpoint, filtered fields). Returns PR details without sensitive fields (userId, account_id, external_id are stripped). Used by the pagador to see what they need to pay. Source: deposit-service / paymentRequest / getPaymentRequestDetailsPublic Access: public ($everyone)

• Coinsenda Flow Createdepositproviderforpr

  [Flow:deposit] Create a PaymentRequestLog (choose payment method for a PR). The pagador selects how to pay (currency + provider_type). The backend creates a PRL which may include a pending Deposit (if create_deposit=true) or a secure combination (if create_deposit=false). Returns the PRL with included deposit and depositProvider relations. VARIANTS (by provider_type): - internal_network: the payer pays with their Coinsenda balance. Returns a PRL (id, state=pending, deposit_id). Pay it via addNew

• Coinsenda Flow Addupdatedepositforpr

  [Flow:deposit] Confirm a deposit for a PaymentRequest (manual confirmation). Used when payment_request_config.create_deposit=true (fiat/bank/internal_network). The pagador submits proof of payment and the deposit transitions to confirmed state. Not applicable for crypto (create_deposit=false) where deposits arrive via blockchain. Source: deposit-service / paymentRequest / addUpdateDepositForPaymentRequest Access: public ($everyone)

• Coinsenda Flow Subscribetonewdeposits

  [Flow:deposit] Subscribe a deposit provider to detect new incoming deposits. Sets sub_to_updates.{currency}=true on the DepositProvider, which causes the fiat deposit listener (runs every 5s) to poll the external provider for new transfers. Detected transfers are automatically created as deposits. Use case: the user wants to check if they received a deposit on a specific provider (e.g. Sphere USD, crypto address). Subscribing triggers detection on the next listener tick. Source: deposit-service

• Coinsenda Flow Openspherebankaccount

  [Flow:deposit] Open a Sphere virtual bank account for USD or EUR. Primary tool when the user asks for USD or EUR receiving details. Each call reads current state and advances only the next safe step. Reinvoke after the user supplies tax data, finishes manual KYC, or the provider finishes API review. COP is out of scope: it uses bank or Bre-B, not Sphere. Source: account-service / account / addNewAccount + identity-service / tax + marketplace-service / sale + deposit-service / depositProvider Acc

• Coinsenda Flow Getfarmproviders

  [Flow:farming] Get available farm (staking) providers. Returns system-wide staking instruments filtered by optional criteria. Only returns providers that are enabled, visible, and in stock. Source: farming-service / farmProvider / find (native LoopBack) Access: user (level_0) Response model (array of farmProvider objects): - id: ObjectID - currency: string (e.g. 'usdt', 'bitcoin') - network: string (e.g. 'cryptocom') - category: string ('onchain_staking', 'defi_staking', 'defi_lending') - user_e

• Coinsenda Flow Getfarms

  [Flow:farming] Get the authenticated user's farms (staking positions). Returns all farms for the current user. Optionally filter by state or currency. Source: farming-service / user / __get__farms (native LoopBack) Access: user ($owner) Response model (array of farm objects): - id: ObjectID - userId: ObjectID - account_id: ObjectID - farm_provider_id: ObjectID - state: string ('pending', 'confirmed', 'accepted', 'rejected', 'canceled') - currency: string - amount_num: string (Decimal128 - staked

• Coinsenda Flow Createfarm

  [Flow:farming] Create a farm (staking position) for the authenticated user. Orchestrates: find eligible provider → find farm account → check balance → create farm. The user only needs to specify currency and amount; the flow resolves everything else. Source: farming-service / farm / addNewFarmPublic Access: user (level_0) Orchestration steps: 1. farmProvider.find() → find provider matching currency + enabled + visible + in stock 2. account.__get__accounts() → find user's farm account for that cu

• Coinsenda Flow Redeemfarm

  [Flow:farming] Redeem (unstake) a farm for the authenticated user. Validates the farm's current state before calling the redeem endpoint, providing descriptive error messages instead of generic error codes. A farm is redeemable when: - state === 'confirmed' - deposited === true - redeemed === false - shares exist (not false/null/0) - expiration_date is null (flexible) or <= now (fixed-term expired) Source: farming-service / farm / redeemFarm Access: user (level_0)