Build Providers.
Get paid.
Ship APIFuse Providers with the public provider-sdk, submit evidence, and earn bounties after maintainer review and merge.
$ bunx @apifuse/provider-sdk@beta create my-provider --yes $ cd my-provider $ bun run check && bun run test ✓ provider scaffolded ✓ checks passed — ready to build
How it works
From an empty directory to a merged provider in four steps. No monorepo access required to start.
Find a bounty
Browse open bounties and pick a target service that matches your tier and skills.
Build with the SDK
Scaffold a standalone provider with the public SDK. Replace the starter operation with real upstream logic, schemas, fixtures, and tests.
Pass the checks
Run check, test, and submit-check locally. Add a real healthCheck per operation and include upstream fixture data.
Submit evidence
Share your workspace branch, SDK version, operation list, health coverage, and command output. Operators review, sync, and merge.
Bounty tiers
Rewards scale with provider complexity. Each open bounty is labeled with its tier.
Simple HTTP providers. 1-2 operations, no auth.
- Public REST endpoints
- Read-only lookups
- No credentials required
Secret-backed or credential-auth providers, 3-5 operations.
- API-key authenticated APIs
- Platform secret usage
- Multi-operation coverage
TLS-sensitive or browser-assisted providers with complex auth.
- CycleTLS-backed transports
- Playwright browser flows
- Multi-step auth ceremonies
Full-featured providers for enterprise APIs.
- Browser + OTP flows
- Large operation surfaces
- Enterprise-grade integrations
Featured bounties
A few high-value bounties to start with. See the full board for all open work.
Toss
toss.im · Account balance, transaction history, and transfers via the Toss app.
KB StarBanking
kbstar.com · Account, transactions, and transfers for KB StarBanking.
Uber (web)
uber.com · Ride booking, fare estimates, and trip status via the web app.
Quick start
You don't need to clone the monorepo. Scaffold, build, and smoke-test a provider entirely with the public SDK.
1 — scaffold & check
mkdir apifuse-bounty && cd apifuse-bounty bunx @apifuse/provider-sdk@beta create my-provider --yes cd my-provider bun run check bun run test bun run dev
2 — smoke an operation
# server runs on port 3900 by default
curl -s http://localhost:3900/health
curl -s -X POST http://localhost:3900/v1/ping \
-H 'Content-Type: application/json' \
-d '{"requestId":"req_local_ping","input":{"value":"hello"},"headers":{}}'generated provider server exposes
GET /healthPOST /v1/{operation}POST /auth/startPOST /auth/continuePOST /auth/pollPOST /auth/disconnectNever commit real credentials. Use .env / shell env for provider secrets and a local-only connection object for credential debugging.
Submission & review
Submit evidence in the invite-only workspace. Operators handle private monorepo sync, registry generation, and deployment.
Evidence to include
- Workspace branch or archive link
- SDK version/tag and create command used
- Provider id, version, runtime, and auth mode
- Operation list with input/output summaries
- Health coverage table: healthCheck or healthCheckUnsupported per operation
- Fixture/test evidence and known upstream rate limits
- bun run check output
- bun run test output
- Local smoke notes for /health and one POST /v1/{operation}
Review criteria
- bun run check passes
- bun run test passes
- Real upstream fixture data included where applicable
- Zod/Standard Schema fields have useful descriptions
- Each operation declares exactly one of healthCheck or healthCheckUnsupported
- Auth, credential, and env secret behavior documented (no real secrets)
Questions
Ready to ship a provider?
Browse open bounties, claim one, and build with the public SDK. Real rewards for real integrations.