User Guide
Advanced

Connect your own site to FloatPass

Give your website Floatboat sign-in, platform credits and payments, with what users spend there recorded as creator credits. You can also offer your API to Floatboat users.

Besides listing on the Floatboat marketplace, you might have a website of your own. Maybe you're a teacher offering an online course, a designer offering templates, or a freelancer offering a handy little tool. FloatPass lets a site like that use Floatboat accounts and credits directly: users sign in to your site with their Floatboat account, top up platform credits, and spend them on the features your site offers.

You don't have to build sign-up, top-ups or a ledger yourself. What users spend on your site is recorded as creator credits in the same account as your marketplace credits, so you redeem everything in one place.

If what you have is an API, you can skip the website and offer it to Floatboat users as an API service, charging credits per call.

You can hand the setup to Floatboat. Download the FloatPass Skill, give the integration prompt to the agent in Floatboat, and it wires FloatPass into your site. If you already write code with Claude Code or Codex, you can give it to them instead. You won't need to write code yourself, but this page explains everything the agent does so you can keep an eye on it.

Requires an active Creator Plan

FloatPass is a Creator Plan benefit. When you create applications or keys, or approve an authorization, your plan must be active, your qualification not suspended, and your business not closed. Not a member yet? See Get qualified to charge.

How credits are recorded

Before you start, here's how what users spend ends up in your account:

  • When users spend platform credits on your site's features, or call your API service, it's recorded as creator credits under the platform rules. The platform rules are what count.
  • Once recorded, it shows up under Recent activity in Creator Data, labeled FloatPass earnings.
  • As with marketplace credits, there's a 30-day wait after they're recorded, and then you can redeem them for Floatboat credits.
  • If a charge is later refunded, returned or compensated to the user, the matching creator credits are taken back.

Open FloatPass

In your browser, open FloatPass in Creator Center and sign in with your Floatboat account.

You can also get there from the app: click your name at the bottom left, choose Creator Center, then click FloatPass on the left.

There are three tabs at the top right:

  • Applications: each website you connect to FloatPass is an application. Its users, credit offers, function prices and transactions are all managed here.
  • Access: download the Skill, copy the integration prompt for your agent, and manage your own Creator Keys.
  • API services: offer your API to Floatboat users.
A browser at floatboat.ai/developer/floatpass, with the Creator Center menu on the left and FloatPass selected; the Access tab is selected at the top right. The Integration resources row has Download Skill, Copy Integration Prompt, Copy Upgrade Prompt and Authorize a device; Copy Integration Prompt is boxed and labelled 1. The Creator Key section below is boxed and labelled 2: a Key name field with a Create key button, and a list with Sam's template shop (Active) and Old site (retired) (Revoked), both with prefixes starting fp_creator_.

Let an agent connect your site

Download the Skill and copy the integration prompt

Open the Access tab. Under Integration resources, click Download Skill and put the downloaded Skill in your website's project folder. Then click Copy Integration Prompt.

The prompt is the agent's task list. It tells the agent to:

  • Ask for your authorization, then reuse or create an application and set your site's real address and the app server key.
  • Wire up email and Google sign-in, with sign-in restored automatically when users come back.
  • Show credit balance and usage on your site and connect top-ups.
  • Charge credits directly when a user clicks a feature button, with no popup, and show the credit price beside the button.
  • Return the original charge to the user when a charge doesn't go through.

The prompt also sets a few rules for the agent:

  • Don't build a separate user system or credit ledger; use FloatPass's.
  • Never charge when a user signs in or a page loads.
  • Don't deploy the Creator Key to the website, and keep every secret out of the browser and out of Git.
  • Keep any wallet your site already has, without migrating it automatically.
  • Check with you before any real payment or deployment.

If your site is already connected and you only want the newer Skill, click Copy Upgrade Prompt and give that to the agent instead.

Give the prompt to your agent

Start a new conversation in Floatboat, paste the integration prompt, and tell it which folder your website project is in, for example "my site's code is in /Users/me/my-site". Then let it start.

If you use Claude Code or Codex, open it in your website's project and paste the integration prompt.

Approve the agent's authorization

When it reaches the step that needs authorization, the agent pauses and gives you an authorization link and a 10-character device code. This step is for you to confirm in person that it really is your agent asking for access. The code is valid for 10 minutes.

Open the link the agent gave you (or click Authorize a device on the Access tab), and sign in to Floatboat if you need to. Enter the code and click Continue.

The page lists the requester, the authorizing account and the authorization name, and spells out the scope: the tool may manage your own applications, application users and payment resources, but it can't touch your creator credits or approve credit adjustments on its own.

If it looks right, click Authorize device. Once you see Device authorized, you can close the page and the agent carries on.

Test first, then go live

Have the agent run through sign-in, top-up, charging and a failed-charge return in a test environment first. Before any real payment or deployment, it will check with you.

Manage your site under Applications

My applications on the Applications tab lists every site you've connected. You can also create one yourself: type a name you'll recognize under Application name and click Create application.

Open an application to see its basics at the top: its AppID (with a copy button), Account mode, Identity status and Sign-in origins.

  • Application settings: change the name and the Allowed sign-in origins, one per line, such as https://app.example.com. Until an origin is set, users can't sign in from your site.
  • Status: pausing, resuming or retiring an application each needs a reason. A retired application can't be restored, and its settings can no longer be changed.

Below that, things are grouped by purpose:

  • Overview: user counts, new and active users in the last 30 days, credits topped up and charged, plus pending requests and payment reviews.
  • Users and support: under Users you can search users, add notes, and disable or restore a user's access to this application. Requests holds refund and credit adjustment requests.
  • Products and pricing: Credit offers are priced in US dollars, and the platform converts the amount into platform credits. Functions sets how many platform credits each feature on your site costs per use.
  • Transactions and credits: Orders and funding, Usage and charges, and Credit ledger show where every payment and credit went.
  • Development: App keys are only for your site's server. Don't put them in web pages or clients.

Refunds and credit adjustments go through a request

To refund a user, return a charge or add credits, submit a refund or credit adjustment request from the application, with the reason and supporting details. It only runs after the platform reviews it, and you can follow it under Requests.

Offer your API to Floatboat users

Open the API services tab. The easiest way is to click Copy for agent, and let the agent read your project's endpoints and register the service for you. You can also Download Skill from here.

To fill it in yourself, first pick an existing application under Service application. If none fits, keep the default, Create a service with a new application, and one is created for you. If you picked an existing application, click New service to open the form. Then:

  1. Fill in Service name, Service code, What the service does, and a public HTTPS POST endpoint.
  2. Choose a Completion mode: Return the result synchronously, or Generate the result asynchronously (then also fill in Task query POST endpoint (same origin), Query interval (seconds) and Maximum wait (minutes)).
  3. Fill in Credits per call (0 is free), plus Version, Data use and retention, and Parameters, response and examples. If your endpoint needs authentication, set up its key under Endpoint authentication.
  4. Click Save draft, then Test the saved draft. The test makes a real request to your endpoint but doesn't charge anyone's credits.
  5. Once the test passes, click Preview publication, and if it's right, click Publish service.

To change a service that's already published, bump its version, test again and publish again. To take it down, use Pause or retire service and give a reason. You can see each call under Calls and credential management.

Manage Creator Keys yourself

A Creator Key is a management key for integration tools. It doesn't go on your website. Usually the authorization flow above is all you need. When you do want to create one by hand, give it a name under Creator Key on the Access tab and click Create key.

The full key is shown only once. Click Copy key right away and keep it somewhere safe. After you leave the page, the list only shows its first few characters (the prefix).

The list shows each key's name, prefix and status (Active or Revoked). If you suspect a key has leaked, click Revoke key and create a new one.

What a key can and can't do

A Creator Key can only manage your own FloatPass resources, such as applications, application users and payment resources. It can't touch your creator credits or approve credit adjustments on its own. So even if one leaks, your creator credits can't be taken. Still, revoke it as soon as you can.

Having trouble?

It says an active Creator Plan is required. Your account hasn't joined the Creator Plan, the plan has expired, or your qualification is suspended. Check its status on the Creator qualification page.

It says the code is invalid or expired. Device codes are only valid for 10 minutes. Go back to the agent, start again, and use the new code.

Users can't sign in from your site. Open the application's settings and make sure your site's real address is in Allowed sign-in origins, and that the application isn't paused or retired.

You can't find a key. A full key can't be shown a second time. Revoke the old one, create a new one, and replace it wherever it was used.

Credits aren't showing up. First check under the application's Usage and charges that the charge actually completed, then look for FloatPass earnings under Recent activity in Creator Data. Newly recorded credits take 30 days before you can redeem them.

What's next

On this page