fluz.app valid

Fluz

The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages.

For agents: Fluz API documentation index with 422 reference pages covering ERP-style resources such as customers, chart of accounts and transactions, plus an API explorer.

fluz apiapi referenceerp integrationaccountingdeveloper dashboard

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T19:10:29.860Z. Cached copy · Source on fluz.app

# Fluz

- [API reference (422 pages)](https://docs.fluz.app/_llms/en/api-reference.txt): Documentation for API reference.

## Home

### Home

- [Fluz API documentation](https://docs.fluz.app/overview.md): Embed money movement into your product — pay-ins, wallets, virtual cards, gift cards, and payouts — through one GraphQL API and a single unified ledger.
- [Changelog](https://docs.fluz.app/changelog.md): Recent updates, additions, and breaking changes to the Fluz API.

### Additional resources

- [Developer dashboard](https://docs.fluz.app/developer-dashboard.md)
- [API explorer](https://docs.fluz.app/api-explorer.md)
- [Go to Fluz app](https://docs.fluz.app/explore-fluz-app.md)

## Get started

### Get started

- [Go from zero to your first API call](https://docs.fluz.app/get-started.md): One GraphQL endpoint. Create your account, generate credentials, exchange them for a scoped access token, and make your first purchase in staging.
- [Introduction to the Fluz API](https://docs.fluz.app/get-started/introduction-to-the-fluz-api.md)
- [Accounts, applications & environments](https://docs.fluz.app/get-started/accounts-and-applications.md): The model to understand before your first call: logins, personal and business accounts, application types and statuses, and which token each operation needs.
- [Design a solution](https://docs.fluz.app/solution-designer.md): Describe what you want to build and get a tailored Fluz solution design.

#### Authentication & authorization

- [Prepare your accounts](https://docs.fluz.app/get-started/prepare-accounts.md): Create your sandbox login, the right type of application, and get it activated — for yourself and for each developer on your team.
- [API credentials and access tokens](https://docs.fluz.app/get-started/api-credentials.md): Exchange your API key for a short-lived, scoped user access token.
- [Make your first API call](https://docs.fluz.app/get-started/first-api-call.md): Run an authenticated GraphQL request against staging and confirm your token works.
- [Refresh an expired access token](https://docs.fluz.app/get-started/refresh-expired-access-token.md): Exchange a refresh token for a fresh user access token without re-minting from scratch.

#### Sandbox test data

- [Test addresses](https://docs.fluz.app/test-addresses.md)
- [Test adding bank cards](https://docs.fluz.app/test-adding-bank-cards.md)
- [Test adding bank accounts](https://docs.fluz.app/test-adding-bank-accounts.md)
- [Test KYC flows](https://docs.fluz.app/test-kyc-flows.md): Run identity verification against staging test identities, and learn which outcomes count as verified.
- [KYB testing](https://docs.fluz.app/KYB-testing.md): Test data for simulating KYB verification outcomes in the staging environment
- [Test gift card purchasing](https://docs.fluz.app/test-merchants.md)
- [Test issuing virtual cards](https://docs.fluz.app/test-issuing-virtual-cards.md): Ready-to-use offer IDs for issuing virtual cards in the staging environment, plus
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=fluz.app · GET /v1/domain/fluz.app · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fluz.app:
1. POST https://agentwebmap.com/v1/sites/fluz.app/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://fluz.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/fluz.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fluz.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.