Register a Yolfi workspace through the public agent registration endpoint when no YOLFI_API_KEY exists yet. This returns an API key once; store it in an ignored env file or secret manager before using private tools.

Verify that YOLFI_API_KEY can authenticate and return the current Yolfi organization context before mutating payment settings.

Read the current Yolfi organization settings, including webhook and settlement configuration visible to this API key.

Update organization profile fields through the existing Yolfi organization endpoint. Do not invent merchant identity, support email, webhook URL, or settlement settings.

Configure settlement wallets after the user provides wallet addresses, networks, and enabled tokens. Never invent wallet addresses.

Configure webhook delivery for the target app. The host must not invent backend URLs and must ensure the app verifies X-Yolfi-Signature.

Create a Yolfi payment link only after the user approves product name, amount, currency, and one-time or recurring payment type.

List existing Yolfi paylinks before creating new ones so agents can avoid duplicates after retries or timeouts.

Get private paylink details by ID for verification, checkout wiring, or duplicate detection.

Disable a paylink. This is destructive and must only run after explicit user confirmation.

Create a public payment invoice from an existing paylink for checkout integration, testing, or customer flow setup.

Get public payment status by ID. Do not treat a frontend redirect as proof of payment.

Verify an X-Yolfi-Signature HMAC over the raw JSON webhook payload before trusting payment events.