slug: meow provider: Meow generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Banking & Capital Markets min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 10 edges: - tag: Invoices spec_file: meow-invoices-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.8 evidence: POST /billing/invoices "Create Invoice"; GET /billing/invoices/{invoice_id}/download "Download Invoice PDF"; schemas Invoice, InvoiceLineRequest, InvoiceStatus reason: Customer invoice creation, retrieval and PDF issuance with payment method options — customer invoicing under accounts receivable management. - tag: Partner Webhooks spec_file: meow-partner-webhooks-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.8 evidence: POST /partner/webhooks/subscriptions "Create Partner Webhook Subscription"; POST /partner/webhooks/deliveries/{delivery_id}/redrive "Redrive Partner Webhook Delivery"; schemas WebhookEventType, WebhookDeliveryAttemptResponse reason: Purely outbound webhook subscription lifecycle, event types and delivery/retry reliability — matches the developer-platform webhook and event subscription capability rather than any banking business capability. - tag: Transfers spec_file: meow-transfers-api-openapi.yml capability_id: BC-1340.10 capability_id_l1: BC-1340 capability_name: Payment Initiation Management confidence: 0.8 evidence: POST /accounts/{account_id}/ach Create ACH Transfer; POST /accounts/{account_id}/wire Create Wire Transfer; POST /accounts/{account_id}/book Create Book Transfer; schema CreateScheduledAchTransferRequest reason: Operations capture and submit payment instructions across ACH, wire, book and crypto rails — payment initiation. Some overlap with payment processing/real-time rails explains the sub-capability ambiguity. - tag: Cards spec_file: meow-cards-api-openapi.yml capability_id: BC-1340.60 capability_id_l1: BC-1340 capability_name: Card Issuance Management confidence: 0.75 evidence: POST /cards "Create Card"; POST /cards/{card_id}/revoke "Revoke Card"; POST /cards/{card_id}/pan "Get Card PAN"; schemas SpendingControls, CardFormFactor, IssuingPlatform reason: Card creation, form factor, PAN retrieval, revocation and spend controls is card issuance lifecycle; the card-transaction listing endpoints are secondary reporting, so the issuance sub-capability is the best fit under Payments & Card Management. - tag: Entities spec_file: meow-entities-api-openapi.yml capability_id: BC-1300.10 capability_id_l1: BC-1300 capability_name: Customer Onboarding Management confidence: 0.75 evidence: GET /entities/{entity_id} "Get Entity Onboarding Status"; POST .../representatives/{representative_id}/kyc "Submit Representative KYC Data"; POST /entities/{entity_id}/submit "Submit Entity Application" reason: 'Business entity account-opening flow: create entity, add representatives, submit KYC and verification links, upload documents, submit application — banking customer onboarding with embedded identity verification.' - tag: Partner Onboarding spec_file: meow-partner-onboarding-api-openapi.yml capability_id: BC-1300.10 capability_id_l1: BC-1300 capability_name: Customer Onboarding Management confidence: 0.75 evidence: POST /partner/applications "Create Application"; POST /partner/applications/{app_id}/kyc "Submit KYC Data"; schemas OnboardingKycStatus, OnboardingApplicationStatus, LegalStructure reason: Application intake, document upload/confirmation and KYC submission with onboarding status tracking — account-opening/onboarding of banking customers via a partner channel. - tag: Webhooks spec_file: meow-webhooks-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.75 evidence: POST /webhooks/subscriptions Create Webhook Subscription; GET /webhooks/deliveries List Webhook Deliveries; POST /webhooks/deliveries/{delivery_id}/redrive Redrive Webhook Delivery reason: Lifecycle of outbound webhook subscriptions plus delivery attempt tracking and redrive — exactly the Webhook & Event Subscription Management capability, which exists explicitly in the candidate list. - tag: Accounts spec_file: meow-accounts-api-openapi.yml capability_id: BC-1330.40 capability_id_l1: BC-1330 capability_name: Account Lifecycle Operations Management confidence: 0.7 evidence: POST /accounts 'Create Bank Account'; POST /accounts/{account_id}/close 'Close a Bank Account'; schemas DepositAccount, OpenableBankProduct reason: Operations open, update and close bank deposit accounts, which is deposit account lifecycle operations. Slight ambiguity between deposit account management and lifecycle operations sub-capabilities. - tag: Bills spec_file: meow-bills-api-openapi.yml capability_id: BC-200.20 capability_id_l1: BC-200 capability_name: Accounts Payable Management confidence: 0.7 evidence: POST /bills create_bill "Create Bill"; schemas "BillPaymentDetailsResponse", "IntegrationVendor", "IntegrationBillPaymentSyncStatus" reason: Operations manage payable bills (vendor bills) with payment details and supporting document upload — invoice-to-pay processing on the buyer side, i.e. accounts payable, not a banking product surface. - tag: Customers spec_file: meow-customers-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.7 evidence: POST /billing/customers "Create Invoicing Customer"; schemas CreateInvoicingCustomerRequest, InvoicingCustomer, AddressRequest reason: Maintains invoicing customer records with billing addresses, i.e. the customer master used for issuing invoices and collecting cash — accounts receivable, not banking customer onboarding.