{
  "skills": [
    {
      "name": "bill-metered-usage",
      "description": "Meter and bill usage-based or consumption pricing with the Fynex Billing API. Use when the user wants usage-based billing, metered billing, pay-as-you-go or consumption pricing, needs to send usage events, define a metric, price API calls or seats, check consumption against an allowance, or find out why metered usage does not match the invoice. Covers metric definition, event ingestion and idempotency, allowances and caps, and corrections.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "build-a-marketplace",
      "description": "Build a two-sided marketplace or platform that takes payments and pays sellers, using Fynex. Use when the user is building a marketplace, multi-vendor store, gig or booking platform, or any product that collects money from buyers and distributes it to sellers, and wants to know the end-to-end shape — onboarding sellers, split payments, commission, payouts and reconciliation. Start here when the request is the whole marketplace rather than one endpoint.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "handle-payouts",
      "description": "Pay sellers, vendors and marketplace recipients out of a Fynex balance. Use when the user wants to pay sellers, send money to a vendor or supplier, withdraw a balance to a bank account, schedule payouts, or work out why a payout failed. Covers creating a payout, which balance it draws on, SEPA and Faster Payments routing, cancelling one before it leaves, and the failure codes with whether a retry can succeed.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "migrate-from-stripe-connect",
      "description": "Move a marketplace or platform from Stripe Connect to Fynex, or compare the two. Use when the user mentions Stripe Connect, connected accounts, destination charges, application_fee_amount, transfer_data, separate charges and transfers, Accounts v2, or asks for a Stripe Connect alternative or how to migrate a platform off Stripe. Maps each Connect concept to its Fynex equivalent, names the three that have no equivalent, and says plainly when staying on Connect is the right call.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "onboard-sellers",
      "description": "Onboard sellers, vendors, sub-merchants and payout recipients onto a Fynex marketplace or platform. Use when the user needs to register sellers, add a vendor or supplier, collect bank details to pay someone, set up a payee, create connected accounts, or ask what a seller must provide before they can be paid. Covers payees, payout methods, the two-call setup shortcut, and which bank identifier format each currency needs.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "reconcile-invoices-to-payouts",
      "description": "Reconcile Fynex invoices, payments, wallet ledger entries and payouts against each other and against a bank statement. Use when the user needs to reconcile, close the books, match an invoice to the payment that settled it or the payout that carried it, export invoices for accounting, explain a balance that does not add up, or trace where a specific amount went. Covers the settlement trail, the wallet ledger, bulk export and the joins that actually hold.",
      "files": [
        "SKILL.md"
      ]
    },
    {
      "name": "split-a-payment",
      "description": "Split payments across multiple recipients with the Fynex Payments API. Use when the user wants to split a payment, divide a charge between a platform and its sellers, take a marketplace commission or platform fee out of a customer payment, do revenue sharing, or send part of one charge to a vendor. Covers percentage and fixed splits, where the platform fee comes from, what happens on a refund, and why there is no separate transfer call.",
      "files": [
        "SKILL.md"
      ]
    }
  ]
}