This commit is contained in:
a2a-platform
2026-06-27 01:02:12 +00:00
commit 145ca85f72
52 changed files with 94532 additions and 0 deletions

11
README.md Normal file
View File

@@ -0,0 +1,11 @@
# plaid-openapi-agent
Generated A2APack agent for The Plaid API.
- Source OpenAPI: https://raw.githubusercontent.com/plaid/plaid-openapi/master/2020-09-14.yml
- Generated operations: 331
- Main skill: `auto`
- Routing mode: DeepAgents subagents across 47 route groups
The generated code is intentionally editable. Tune prompts, operation
grouping, auth names, and safety policy before publishing serious agents.

12
a2a.yaml Normal file
View File

@@ -0,0 +1,12 @@
name: plaid-openapi-agent
version: 2020-09-14_1.698.7
entrypoint: agent:PlaidOpenapiAgent
description: Financial data API for bank linking, transactions, identity, and payments.
runtime:
resources:
cpu: 200m
memory: 512Mi
egress:
allow_hosts:
- production.plaid.com
deny_internet_by_default: true

436
agent.py Normal file

File diff suppressed because one or more lines are too long

90745
openapi.json Normal file

File diff suppressed because it is too large Load Diff

7
requirements.txt Normal file
View File

@@ -0,0 +1,7 @@
# a2a-pack is installed by the platform base image.
deepagents>=0.5.0
langchain>=0.3
langchain-openai>=0.2
langchain-core>=0.3
langgraph>=0.6
httpx>=0.27

30
skills/accounts/SKILL.md Normal file
View File

@@ -0,0 +1,30 @@
---
name: accounts-routes
description: Handle 2 OpenAPI operation(s) under /accounts for the accounts route group.
---
# accounts API Routes
Handle 2 OpenAPI operation(s) under /accounts for the accounts route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### accounts_get
- Operation ID: `accounts_get`
- Route: `POST /accounts/get`
- Mode: WRITE
- Summary: Retrieve accounts
- Body: JSON request body accepted.
### accounts_balance_get
- Operation ID: `accounts_balance_get`
- Route: `POST /accounts/balance/get`
- Mode: WRITE
- Summary: Retrieve real-time balance data
- Body: JSON request body accepted.

View File

@@ -0,0 +1,22 @@
---
name: application-routes
description: Handle 1 OpenAPI operation(s) under /application/get for the application route group.
---
# application API Routes
Handle 1 OpenAPI operation(s) under /application/get for the application route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### application_get
- Operation ID: `application_get`
- Route: `POST /application/get`
- Mode: WRITE
- Summary: Retrieve information about a Plaid application
- Body: JSON request body accepted.

View File

@@ -0,0 +1,94 @@
---
name: asset-report-routes
description: Handle 10 OpenAPI operation(s) under /asset_report for the asset report route group.
---
# asset report API Routes
Handle 10 OpenAPI operation(s) under /asset_report for the asset report route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### asset_report_create
- Operation ID: `asset_report_create`
- Route: `POST /asset_report/create`
- Mode: WRITE
- Summary: Create an Asset Report
- Body: JSON request body accepted.
### asset_report_get
- Operation ID: `asset_report_get`
- Route: `POST /asset_report/get`
- Mode: WRITE
- Summary: Retrieve an Asset Report
- Body: JSON request body accepted.
### asset_report_pdf_get
- Operation ID: `asset_report_pdf_get`
- Route: `POST /asset_report/pdf/get`
- Mode: WRITE
- Summary: Retrieve a PDF Asset Report
- Body: JSON request body accepted.
### asset_report_refresh
- Operation ID: `asset_report_refresh`
- Route: `POST /asset_report/refresh`
- Mode: WRITE
- Summary: Refresh an Asset Report
- Body: JSON request body accepted.
### asset_report_filter
- Operation ID: `asset_report_filter`
- Route: `POST /asset_report/filter`
- Mode: WRITE
- Summary: Filter Asset Report
- Body: JSON request body accepted.
### asset_report_remove
- Operation ID: `asset_report_remove`
- Route: `POST /asset_report/remove`
- Mode: WRITE
- Summary: Delete an Asset Report
- Body: JSON request body accepted.
### asset_report_audit_copy_create
- Operation ID: `asset_report_audit_copy_create`
- Route: `POST /asset_report/audit_copy/create`
- Mode: WRITE
- Summary: Create Asset Report Audit Copy
- Body: JSON request body accepted.
### asset_report_audit_copy_get
- Operation ID: `asset_report_audit_copy_get`
- Route: `POST /asset_report/audit_copy/get`
- Mode: WRITE
- Summary: Retrieve an Asset Report Audit Copy
- Body: JSON request body accepted.
### asset_report_audit_copy_pdf_get
- Operation ID: `asset_report_audit_copy_pdf_get`
- Route: `POST /asset_report/audit_copy/pdf/get`
- Mode: WRITE
- Summary: Retrieve a PDF Asset Report Audit Copy
- Body: JSON request body accepted.
### asset_report_audit_copy_remove
- Operation ID: `asset_report_audit_copy_remove`
- Route: `POST /asset_report/audit_copy/remove`
- Mode: WRITE
- Summary: Remove Asset Report Audit Copy
- Body: JSON request body accepted.

30
skills/auth/SKILL.md Normal file
View File

@@ -0,0 +1,30 @@
---
name: auth-routes
description: Handle 2 OpenAPI operation(s) under /auth for the auth route group.
---
# auth API Routes
Handle 2 OpenAPI operation(s) under /auth for the auth route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### auth_get
- Operation ID: `auth_get`
- Route: `POST /auth/get`
- Mode: WRITE
- Summary: Retrieve auth data
- Body: JSON request body accepted.
### auth_verify
- Operation ID: `auth_verify`
- Route: `POST /auth/verify`
- Mode: WRITE
- Summary: Verify auth data
- Body: JSON request body accepted.

View File

@@ -0,0 +1,94 @@
---
name: bank-transfer-routes
description: Handle 10 OpenAPI operation(s) under /bank_transfer for the bank transfer route group.
---
# bank transfer API Routes
Handle 10 OpenAPI operation(s) under /bank_transfer for the bank transfer route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### bank_transfer_get
- Operation ID: `bank_transfer_get`
- Route: `POST /bank_transfer/get`
- Mode: WRITE
- Summary: Retrieve a bank transfer
- Body: JSON request body accepted.
### bank_transfer_create
- Operation ID: `bank_transfer_create`
- Route: `POST /bank_transfer/create`
- Mode: WRITE
- Summary: Create a bank transfer
- Body: JSON request body accepted.
### bank_transfer_list
- Operation ID: `bank_transfer_list`
- Route: `POST /bank_transfer/list`
- Mode: WRITE
- Summary: List bank transfers
- Body: JSON request body accepted.
### bank_transfer_cancel
- Operation ID: `bank_transfer_cancel`
- Route: `POST /bank_transfer/cancel`
- Mode: WRITE
- Summary: Cancel a bank transfer
- Body: JSON request body accepted.
### bank_transfer_event_list
- Operation ID: `bank_transfer_event_list`
- Route: `POST /bank_transfer/event/list`
- Mode: WRITE
- Summary: List bank transfer events
- Body: JSON request body accepted.
### bank_transfer_event_sync
- Operation ID: `bank_transfer_event_sync`
- Route: `POST /bank_transfer/event/sync`
- Mode: WRITE
- Summary: Sync bank transfer events
- Body: JSON request body accepted.
### bank_transfer_sweep_get
- Operation ID: `bank_transfer_sweep_get`
- Route: `POST /bank_transfer/sweep/get`
- Mode: WRITE
- Summary: Retrieve a sweep
- Body: JSON request body accepted.
### bank_transfer_sweep_list
- Operation ID: `bank_transfer_sweep_list`
- Route: `POST /bank_transfer/sweep/list`
- Mode: WRITE
- Summary: List sweeps
- Body: JSON request body accepted.
### bank_transfer_balance_get
- Operation ID: `bank_transfer_balance_get`
- Route: `POST /bank_transfer/balance/get`
- Mode: WRITE
- Summary: Get balance of your Bank Transfer account
- Body: JSON request body accepted.
### bank_transfer_migrate_account
- Operation ID: `bank_transfer_migrate_account`
- Route: `POST /bank_transfer/migrate_account`
- Mode: WRITE
- Summary: Migrate account into Bank Transfers
- Body: JSON request body accepted.

118
skills/beacon/SKILL.md Normal file
View File

@@ -0,0 +1,118 @@
---
name: beacon-routes
description: Handle 13 OpenAPI operation(s) under /beacon for the beacon route group.
---
# beacon API Routes
Handle 13 OpenAPI operation(s) under /beacon for the beacon route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### beacon_account_risk_evaluate
- Operation ID: `beacon_account_risk_evaluate`
- Route: `POST /beacon/account_risk/v1/evaluate`
- Mode: WRITE
- Summary: Evaluate risk of a bank account
- Body: JSON request body accepted.
### beacon_user_create
- Operation ID: `beacon_user_create`
- Route: `POST /beacon/user/create`
- Mode: WRITE
- Summary: Create a Beacon User
- Body: JSON request body accepted.
### beacon_user_get
- Operation ID: `beacon_user_get`
- Route: `POST /beacon/user/get`
- Mode: WRITE
- Summary: Get a Beacon User
- Body: JSON request body accepted.
### beacon_user_review
- Operation ID: `beacon_user_review`
- Route: `POST /beacon/user/review`
- Mode: WRITE
- Summary: Review a Beacon User
- Body: JSON request body accepted.
### beacon_report_create
- Operation ID: `beacon_report_create`
- Route: `POST /beacon/report/create`
- Mode: WRITE
- Summary: Create a Beacon Report
- Body: JSON request body accepted.
### beacon_report_list
- Operation ID: `beacon_report_list`
- Route: `POST /beacon/report/list`
- Mode: WRITE
- Summary: List Beacon Reports for a Beacon User
- Body: JSON request body accepted.
### beacon_report_syndication_list
- Operation ID: `beacon_report_syndication_list`
- Route: `POST /beacon/report_syndication/list`
- Mode: WRITE
- Summary: List Beacon Report Syndications for a Beacon User
- Body: JSON request body accepted.
### beacon_report_get
- Operation ID: `beacon_report_get`
- Route: `POST /beacon/report/get`
- Mode: WRITE
- Summary: Get a Beacon Report
- Body: JSON request body accepted.
### beacon_report_syndication_get
- Operation ID: `beacon_report_syndication_get`
- Route: `POST /beacon/report_syndication/get`
- Mode: WRITE
- Summary: Get a Beacon Report Syndication
- Body: JSON request body accepted.
### beacon_user_update
- Operation ID: `beacon_user_update`
- Route: `POST /beacon/user/update`
- Mode: WRITE
- Summary: Update the identity data of a Beacon User
- Body: JSON request body accepted.
### beacon_duplicate_get
- Operation ID: `beacon_duplicate_get`
- Route: `POST /beacon/duplicate/get`
- Mode: WRITE
- Summary: Get a Beacon Duplicate
- Body: JSON request body accepted.
### beacon_user_history_list
- Operation ID: `beacon_user_history_list`
- Route: `POST /beacon/user/history/list`
- Mode: WRITE
- Summary: List a Beacon User's history
- Body: JSON request body accepted.
### beacon_user_account_insights_get
- Operation ID: `beacon_user_account_insights_get`
- Route: `POST /beacon/user/account_insights/get`
- Mode: WRITE
- Summary: Get Account Insights for a Beacon User
- Body: JSON request body accepted.

102
skills/beta/SKILL.md Normal file
View File

@@ -0,0 +1,102 @@
---
name: beta-routes
description: Handle 11 OpenAPI operation(s) under /beta for the beta route group.
---
# beta API Routes
Handle 11 OpenAPI operation(s) under /beta for the beta route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### credit_bank_employment_get
- Operation ID: `credit_bank_employment_get`
- Route: `POST /beta/credit/v1/bank_employment/get`
- Mode: WRITE
- Summary: Retrieve information from the bank accounts used for employment verification
- Body: JSON request body accepted.
### transactions_enhance
- Operation ID: `transactions_enhance`
- Route: `POST /beta/transactions/v1/enhance`
- Mode: WRITE
- Summary: Enhance locally-held transaction data
- Body: JSON request body accepted.
### transactions_rules_create
- Operation ID: `transactions_rules_create`
- Route: `POST /beta/transactions/rules/v1/create`
- Mode: WRITE
- Summary: Create transaction category rule
- Body: JSON request body accepted.
### transactions_rules_list
- Operation ID: `transactions_rules_list`
- Route: `POST /beta/transactions/rules/v1/list`
- Mode: WRITE
- Summary: Return a list of rules created for the Item associated with the access token.
- Body: JSON request body accepted.
### transactions_rules_remove
- Operation ID: `transactions_rules_remove`
- Route: `POST /beta/transactions/rules/v1/remove`
- Mode: WRITE
- Summary: Remove transaction rule
- Body: JSON request body accepted.
### transactions_user_insights_get
- Operation ID: `transactions_user_insights_get`
- Route: `POST /beta/transactions/user_insights/v1/get`
- Mode: WRITE
- Summary: Obtain user insights based on transactions sent through /transactions/enrich
- Body: JSON request body accepted.
### beta_ewa_report_v1_get
- Operation ID: `beta_ewa_report_v1_get`
- Route: `POST /beta/ewa_report/v1/get`
- Mode: WRITE
- Summary: Get EWA Score Report
- Body: JSON request body accepted.
### beta_partner_customer_v1_create
- Operation ID: `beta_partner_customer_v1_create`
- Route: `POST /beta/partner/customer/v1/create`
- Mode: WRITE
- Summary: Creates a new end customer for a Plaid reseller.
- Body: JSON request body accepted.
### beta_partner_customer_v1_get
- Operation ID: `beta_partner_customer_v1_get`
- Route: `POST /beta/partner/customer/v1/get`
- Mode: WRITE
- Summary: Retrieves the details of a Plaid reseller's end customer.
- Body: JSON request body accepted.
### beta_partner_customer_v1_update
- Operation ID: `beta_partner_customer_v1_update`
- Route: `POST /beta/partner/customer/v1/update`
- Mode: WRITE
- Summary: Updates an existing end customer.
- Body: JSON request body accepted.
### beta_partner_customer_v1_enable
- Operation ID: `beta_partner_customer_v1_enable`
- Route: `POST /beta/partner/customer/v1/enable`
- Mode: WRITE
- Summary: Enables a Plaid reseller's end customer in the Production environment.
- Body: JSON request body accepted.

View File

@@ -0,0 +1,30 @@
---
name: business-verification-routes
description: Handle 2 OpenAPI operation(s) under /business_verification for the business verification route group.
---
# business verification API Routes
Handle 2 OpenAPI operation(s) under /business_verification for the business verification route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### business_verification_get
- Operation ID: `business_verification_get`
- Route: `POST /business_verification/get`
- Mode: WRITE
- Summary: Get a Business Verification
- Body: JSON request body accepted.
### business_verification_create
- Operation ID: `business_verification_create`
- Route: `POST /business_verification/create`
- Mode: WRITE
- Summary: Create a Business Verification
- Body: JSON request body accepted.

View File

@@ -0,0 +1,46 @@
---
name: cashflow-report-routes
description: Handle 4 OpenAPI operation(s) under /cashflow_report for the cashflow report route group.
---
# cashflow report API Routes
Handle 4 OpenAPI operation(s) under /cashflow_report for the cashflow report route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### cashflow_report_refresh
- Operation ID: `cashflow_report_refresh`
- Route: `POST /cashflow_report/refresh`
- Mode: WRITE
- Summary: Refresh transaction data in `cashflow_report`
- Body: JSON request body accepted.
### cashflow_report_get
- Operation ID: `cashflow_report_get`
- Route: `POST /cashflow_report/get`
- Mode: WRITE
- Summary: Gets transaction data in `cashflow_report`
- Body: JSON request body accepted.
### cashflow_report_transactions_get
- Operation ID: `cashflow_report_transactions_get`
- Route: `POST /cashflow_report/transactions/get`
- Mode: WRITE
- Summary: Gets transaction data in `cashflow_report`
- Body: JSON request body accepted.
### cashflow_report_insights_get
- Operation ID: `cashflow_report_insights_get`
- Route: `POST /cashflow_report/insights/get`
- Mode: WRITE
- Summary: Gets insights data in Cashflow Report
- Body: JSON request body accepted.

View File

@@ -0,0 +1,22 @@
---
name: categories-routes
description: Handle 1 OpenAPI operation(s) under /categories/get for the categories route group.
---
# categories API Routes
Handle 1 OpenAPI operation(s) under /categories/get for the categories route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### categories_get
- Operation ID: `categories_get`
- Route: `POST /categories/get`
- Mode: WRITE
- Summary: (Deprecated) Get legacy categories
- Body: JSON request body accepted.

22
skills/consent/SKILL.md Normal file
View File

@@ -0,0 +1,22 @@
---
name: consent-routes
description: Handle 1 OpenAPI operation(s) under /consent/events/get for the consent route group.
---
# consent API Routes
Handle 1 OpenAPI operation(s) under /consent/events/get for the consent route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### consent_events_get
- Operation ID: `consent_events_get`
- Route: `POST /consent/events/get`
- Mode: WRITE
- Summary: List a historical log of item consent events
- Body: JSON request body accepted.

View File

@@ -0,0 +1,22 @@
---
name: consumer-report-routes
description: Handle 1 OpenAPI operation(s) under /consumer_report/pdf/get for the consumer report route group.
---
# consumer report API Routes
Handle 1 OpenAPI operation(s) under /consumer_report/pdf/get for the consumer report route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### consumer_report_pdf_get
- Operation ID: `consumer_report_pdf_get`
- Route: `POST /consumer_report/pdf/get`
- Mode: WRITE
- Summary: Retrieve PDF Reports
- Body: JSON request body accepted.

166
skills/cra/SKILL.md Normal file
View File

@@ -0,0 +1,166 @@
---
name: cra-routes
description: Handle 19 OpenAPI operation(s) under /cra for the cra route group.
---
# cra API Routes
Handle 19 OpenAPI operation(s) under /cra for the cra route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### cra_monitoring_insights_subscribe
- Operation ID: `cra_monitoring_insights_subscribe`
- Route: `POST /cra/monitoring_insights/subscribe`
- Mode: WRITE
- Summary: Subscribe to Monitoring Insights
- Body: JSON request body accepted.
### cra_monitoring_insights_unsubscribe
- Operation ID: `cra_monitoring_insights_unsubscribe`
- Route: `POST /cra/monitoring_insights/unsubscribe`
- Mode: WRITE
- Summary: Unsubscribe from Monitoring Insights
- Body: JSON request body accepted.
### cra_monitoring_insights_get
- Operation ID: `cra_monitoring_insights_get`
- Route: `POST /cra/monitoring_insights/get`
- Mode: WRITE
- Summary: Retrieve a Monitoring Insights Report
- Body: JSON request body accepted.
### cra_partner_insights_get
- Operation ID: `cra_partner_insights_get`
- Route: `POST /cra/partner_insights/get`
- Mode: WRITE
- Summary: Retrieve cash flow insights from the bank accounts used for income verification
- Body: JSON request body accepted.
### cra_check_report_income_insights_get
- Operation ID: `cra_check_report_income_insights_get`
- Route: `POST /cra/check_report/income_insights/get`
- Mode: WRITE
- Summary: Retrieve cash flow information from your user's banks
- Body: JSON request body accepted.
### cra_check_report_base_report_get
- Operation ID: `cra_check_report_base_report_get`
- Route: `POST /cra/check_report/base_report/get`
- Mode: WRITE
- Summary: Retrieve a Base Report
- Body: JSON request body accepted.
### cra_check_report_pdf_get
- Operation ID: `cra_check_report_pdf_get`
- Route: `POST /cra/check_report/pdf/get`
- Mode: WRITE
- Summary: Retrieve a Consumer Report as a PDF
- Body: JSON request body accepted.
### cra_check_report_create
- Operation ID: `cra_check_report_create`
- Route: `POST /cra/check_report/create`
- Mode: WRITE
- Summary: Refresh or create a Consumer Report
- Body: JSON request body accepted.
### cra_check_report_partner_insights_get
- Operation ID: `cra_check_report_partner_insights_get`
- Route: `POST /cra/check_report/partner_insights/get`
- Mode: WRITE
- Summary: Retrieve cash flow insights from partners
- Body: JSON request body accepted.
### cra_check_report_cashflow_insights_get
- Operation ID: `cra_check_report_cashflow_insights_get`
- Route: `POST /cra/check_report/cashflow_insights/get`
- Mode: WRITE
- Summary: Retrieve cash flow insights from your user's banking data
- Body: JSON request body accepted.
### cra_check_report_lend_score_get
- Operation ID: `cra_check_report_lend_score_get`
- Route: `POST /cra/check_report/lend_score/get`
- Mode: WRITE
- Summary: Retrieve the LendScore from your user's banking data
- Body: JSON request body accepted.
### cra_check_report_network_insights_get
- Operation ID: `cra_check_report_network_insights_get`
- Route: `POST /cra/check_report/network_insights/get`
- Mode: WRITE
- Summary: Retrieve network attributes for the user
- Body: JSON request body accepted.
### cra_check_report_verification_get
- Operation ID: `cra_check_report_verification_get`
- Route: `POST /cra/check_report/verification/get`
- Mode: WRITE
- Summary: Retrieve various home lending reports for a user
- Body: JSON request body accepted.
### cra_check_report_verification_pdf_get
- Operation ID: `cra_check_report_verification_pdf_get`
- Route: `POST /cra/check_report/verification/pdf/get`
- Mode: WRITE
- Summary: Retrieve a Consumer Report as a Verification PDF
- Body: JSON request body accepted.
### cra_loans_applications_register
- Operation ID: `cra_loans_applications_register`
- Route: `POST /cra/loans/applications/register`
- Mode: WRITE
- Summary: Register loan applications and decisions
- Body: JSON request body accepted.
### cra_loans_register
- Operation ID: `cra_loans_register`
- Route: `POST /cra/loans/register`
- Mode: WRITE
- Summary: Register a list of loans to their applicants
- Body: JSON request body accepted.
### cra_loans_update
- Operation ID: `cra_loans_update`
- Route: `POST /cra/loans/update`
- Mode: WRITE
- Summary: Update loan data
- Body: JSON request body accepted.
### cra_loans_unregister
- Operation ID: `cra_loans_unregister`
- Route: `POST /cra/loans/unregister`
- Mode: WRITE
- Summary: Unregister a list of loans
- Body: JSON request body accepted.
### cra_credit_profile_report_get
- Operation ID: `cra_credit_profile_report_get`
- Route: `POST /cra/credit_profile/report/get`
- Mode: WRITE
- Summary: Retrieve the credit profile report for a user
- Body: JSON request body accepted.

190
skills/credit/SKILL.md Normal file
View File

@@ -0,0 +1,190 @@
---
name: credit-routes
description: Handle 22 OpenAPI operation(s) under /credit for the credit route group.
---
# credit API Routes
Handle 22 OpenAPI operation(s) under /credit for the credit route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### credit_audit_copy_token_update
- Operation ID: `credit_audit_copy_token_update`
- Route: `POST /credit/audit_copy_token/update`
- Mode: WRITE
- Summary: Update an Audit Copy Token
- Body: JSON request body accepted.
### credit_sessions_get
- Operation ID: `credit_sessions_get`
- Route: `POST /credit/sessions/get`
- Mode: WRITE
- Summary: Retrieve Link sessions for your user
- Body: JSON request body accepted.
### credit_audit_copy_token_create
- Operation ID: `credit_audit_copy_token_create`
- Route: `POST /credit/audit_copy_token/create`
- Mode: WRITE
- Summary: Create Asset or Income Report Audit Copy Token
- Body: JSON request body accepted.
### credit_report_audit_copy_remove
- Operation ID: `credit_report_audit_copy_remove`
- Route: `POST /credit/audit_copy_token/remove`
- Mode: WRITE
- Summary: Remove an Audit Copy token
- Body: JSON request body accepted.
### credit_asset_report_freddie_mac_get
- Operation ID: `credit_asset_report_freddie_mac_get`
- Route: `POST /credit/asset_report/freddie_mac/get`
- Mode: WRITE
- Summary: Retrieve an Asset Report with Freddie Mac format. Only Freddie Mac can use this endpoint.
- Body: JSON request body accepted.
### credit_freddie_mac_reports_get
- Operation ID: `credit_freddie_mac_reports_get`
- Route: `POST /credit/freddie_mac/reports/get`
- Mode: WRITE
- Summary: Retrieve an Asset Report with Freddie Mac format (aka VOA - Verification Of Assets), and a Verification Of Employment (VOE) report if this one is available. Only Freddie Mac can use this endpoint.
- Body: JSON request body accepted.
### credit_bank_income_get
- Operation ID: `credit_bank_income_get`
- Route: `POST /credit/bank_income/get`
- Mode: WRITE
- Summary: Retrieve information from the bank accounts used for income verification
- Body: JSON request body accepted.
### credit_bank_income_pdf_get
- Operation ID: `credit_bank_income_pdf_get`
- Route: `POST /credit/bank_income/pdf/get`
- Mode: WRITE
- Summary: Retrieve information from the bank accounts used for income verification in PDF format
- Body: JSON request body accepted.
### credit_bank_income_refresh
- Operation ID: `credit_bank_income_refresh`
- Route: `POST /credit/bank_income/refresh`
- Mode: WRITE
- Summary: Refresh a user's bank income information
- Body: JSON request body accepted.
### credit_bank_income_webhook_update
- Operation ID: `credit_bank_income_webhook_update`
- Route: `POST /credit/bank_income/webhook/update`
- Mode: WRITE
- Summary: Subscribe and unsubscribe to proactive notifications for a user's income profile
- Body: JSON request body accepted.
### credit_payroll_income_parsing_config_update
- Operation ID: `credit_payroll_income_parsing_config_update`
- Route: `POST /credit/payroll_income/parsing_config/update`
- Mode: WRITE
- Summary: Update the parsing configuration for a document income verification
- Body: JSON request body accepted.
### credit_bank_statements_uploads_get
- Operation ID: `credit_bank_statements_uploads_get`
- Route: `POST /credit/bank_statements/uploads/get`
- Mode: WRITE
- Summary: Retrieve data for a user's uploaded bank statements
- Body: JSON request body accepted.
### credit_payroll_income_get
- Operation ID: `credit_payroll_income_get`
- Route: `POST /credit/payroll_income/get`
- Mode: WRITE
- Summary: Retrieve a user's payroll information
- Body: JSON request body accepted.
### credit_payroll_income_risk_signals_get
- Operation ID: `credit_payroll_income_risk_signals_get`
- Route: `POST /credit/payroll_income/risk_signals/get`
- Mode: WRITE
- Summary: Retrieve fraud insights for a user's manually uploaded document(s).
- Body: JSON request body accepted.
### credit_payroll_income_precheck
- Operation ID: `credit_payroll_income_precheck`
- Route: `POST /credit/payroll_income/precheck`
- Mode: WRITE
- Summary: Check income verification eligibility and optimize conversion
- Body: JSON request body accepted.
### credit_employment_get
- Operation ID: `credit_employment_get`
- Route: `POST /credit/employment/get`
- Mode: WRITE
- Summary: Retrieve a summary of an individual's employment information
- Body: JSON request body accepted.
### credit_payroll_income_refresh
- Operation ID: `credit_payroll_income_refresh`
- Route: `POST /credit/payroll_income/refresh`
- Mode: WRITE
- Summary: Refresh a digital payroll income verification
- Body: JSON request body accepted.
### credit_relay_create
- Operation ID: `credit_relay_create`
- Route: `POST /credit/relay/create`
- Mode: WRITE
- Summary: Create a relay token to share an Asset Report with a partner client
- Body: JSON request body accepted.
### credit_relay_get
- Operation ID: `credit_relay_get`
- Route: `POST /credit/relay/get`
- Mode: WRITE
- Summary: Retrieve the reports associated with a relay token that was shared with you
- Body: JSON request body accepted.
### credit_relay_pdf_get
- Operation ID: `credit_relay_pdf_get`
- Route: `POST /credit/relay/pdf/get`
- Mode: WRITE
- Summary: Retrieve the pdf reports associated with a relay token that was shared with you (beta)
- Body: JSON request body accepted.
### credit_relay_refresh
- Operation ID: `credit_relay_refresh`
- Route: `POST /credit/relay/refresh`
- Mode: WRITE
- Summary: Refresh a report of a relay token
- Body: JSON request body accepted.
### credit_relay_remove
- Operation ID: `credit_relay_remove`
- Route: `POST /credit/relay/remove`
- Mode: WRITE
- Summary: Remove relay token
- Body: JSON request body accepted.

View File

@@ -0,0 +1,30 @@
---
name: dashboard-user-routes
description: Handle 2 OpenAPI operation(s) under /dashboard_user for the dashboard user route group.
---
# dashboard user API Routes
Handle 2 OpenAPI operation(s) under /dashboard_user for the dashboard user route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### dashboard_user_get
- Operation ID: `dashboard_user_get`
- Route: `POST /dashboard_user/get`
- Mode: WRITE
- Summary: Retrieve a Dashboard user
- Body: JSON request body accepted.
### dashboard_user_list
- Operation ID: `dashboard_user_list`
- Route: `POST /dashboard_user/list`
- Mode: WRITE
- Summary: List Dashboard users
- Body: JSON request body accepted.

22
skills/employers/SKILL.md Normal file
View File

@@ -0,0 +1,22 @@
---
name: employers-routes
description: Handle 1 OpenAPI operation(s) under /employers/search for the employers route group.
---
# employers API Routes
Handle 1 OpenAPI operation(s) under /employers/search for the employers route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### employers_search
- Operation ID: `employers_search`
- Route: `POST /employers/search`
- Mode: WRITE
- Summary: Search employer database
- Body: JSON request body accepted.

View File

@@ -0,0 +1,22 @@
---
name: employment-routes
description: Handle 1 OpenAPI operation(s) under /employment/verification/get for the employment route group.
---
# employment API Routes
Handle 1 OpenAPI operation(s) under /employment/verification/get for the employment route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### employment_verification_get
- Operation ID: `employment_verification_get`
- Route: `POST /employment/verification/get`
- Mode: WRITE
- Summary: (Deprecated) Retrieve a summary of an individual's employment information
- Body: JSON request body accepted.

67
skills/fdx/SKILL.md Normal file
View File

@@ -0,0 +1,67 @@
---
name: fdx-routes
description: Handle 6 OpenAPI operation(s) under /fdx for the fdx route group.
---
# fdx API Routes
Handle 6 OpenAPI operation(s) under /fdx for the fdx route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### fdx_notifications
- Operation ID: `fdx_notifications`
- Route: `POST /fdx/notifications`
- Mode: WRITE
- Summary: Webhook receiver for fdx notifications
- Body: JSON request body accepted.
### get_recipients
- Operation ID: `get_recipients`
- Route: `GET /fdx/recipients`
- Mode: READ
- Summary: Get Recipients
### fdx_consents_revoke
- Operation ID: `fdx_consents_revoke`
- Route: `PUT /fdx/consents/{consentId}/revocation`
- Mode: WRITE
- Summary: Revoke FDX Consent Grant
- Parameters:
- `consentId` in `path` required
- Body: JSON request body accepted.
### fdx_consents_revocation_get
- Operation ID: `fdx_consents_revocation_get`
- Route: `GET /fdx/consents/{consentId}/revocation`
- Mode: READ
- Summary: Retrieve FDX Consent Grant revocation records
- Parameters:
- `consentId` in `path` required
### fdx_consents_get
- Operation ID: `fdx_consents_get`
- Route: `GET /fdx/consents/{consentId}`
- Mode: READ
- Summary: Get FDX Consent Grant
- Parameters:
- `consentId` in `path` required
### get_recipient
- Operation ID: `get_recipient`
- Route: `GET /fdx/recipient/{recipientId}`
- Mode: READ
- Summary: Get Recipient
- Parameters:
- `recipientId` in `path` required
- `OAUTH-STATE-ID` in `header`

View File

@@ -0,0 +1,54 @@
---
name: identity-verification-routes
description: Handle 5 OpenAPI operation(s) under /identity_verification for the identity verification route group.
---
# identity verification API Routes
Handle 5 OpenAPI operation(s) under /identity_verification for the identity verification route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### identity_verification_create
- Operation ID: `identity_verification_create`
- Route: `POST /identity_verification/create`
- Mode: WRITE
- Summary: Create a new Identity Verification
- Body: JSON request body accepted.
### identity_verification_get
- Operation ID: `identity_verification_get`
- Route: `POST /identity_verification/get`
- Mode: WRITE
- Summary: Retrieve Identity Verification
- Body: JSON request body accepted.
### identity_verification_list
- Operation ID: `identity_verification_list`
- Route: `POST /identity_verification/list`
- Mode: WRITE
- Summary: List Identity Verifications
- Body: JSON request body accepted.
### identity_verification_retry
- Operation ID: `identity_verification_retry`
- Route: `POST /identity_verification/retry`
- Mode: WRITE
- Summary: Retry an Identity Verification
- Body: JSON request body accepted.
### identity_verification_autofill_create
- Operation ID: `identity_verification_autofill_create`
- Route: `POST /identity_verification/autofill/create`
- Mode: WRITE
- Summary: Create autofill for an Identity Verification
- Body: JSON request body accepted.

46
skills/identity/SKILL.md Normal file
View File

@@ -0,0 +1,46 @@
---
name: identity-routes
description: Handle 4 OpenAPI operation(s) under /identity for the identity route group.
---
# identity API Routes
Handle 4 OpenAPI operation(s) under /identity for the identity route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### identity_get
- Operation ID: `identity_get`
- Route: `POST /identity/get`
- Mode: WRITE
- Summary: Retrieve identity data
- Body: JSON request body accepted.
### identity_documents_uploads_get
- Operation ID: `identity_documents_uploads_get`
- Route: `POST /identity/documents/uploads/get`
- Mode: WRITE
- Summary: Returns uploaded document identity
- Body: JSON request body accepted.
### identity_match
- Operation ID: `identity_match`
- Route: `POST /identity/match`
- Mode: WRITE
- Summary: Retrieve identity match score
- Body: JSON request body accepted.
### identity_refresh
- Operation ID: `identity_refresh`
- Route: `POST /identity/refresh`
- Mode: WRITE
- Summary: Refresh identity data
- Body: JSON request body accepted.

54
skills/income/SKILL.md Normal file
View File

@@ -0,0 +1,54 @@
---
name: income-routes
description: Handle 5 OpenAPI operation(s) under /income/verification for the income route group.
---
# income API Routes
Handle 5 OpenAPI operation(s) under /income/verification for the income route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### income_verification_create
- Operation ID: `income_verification_create`
- Route: `POST /income/verification/create`
- Mode: WRITE
- Summary: (Deprecated) Create an income verification instance
- Body: JSON request body accepted.
### income_verification_paystubs_get
- Operation ID: `income_verification_paystubs_get`
- Route: `POST /income/verification/paystubs/get`
- Mode: WRITE
- Summary: (Deprecated) Retrieve information from the paystubs used for income verification
- Body: JSON request body accepted.
### income_verification_documents_download
- Operation ID: `income_verification_documents_download`
- Route: `POST /income/verification/documents/download`
- Mode: WRITE
- Summary: (Deprecated) Download the original documents used for income verification
- Body: JSON request body accepted.
### income_verification_taxforms_get
- Operation ID: `income_verification_taxforms_get`
- Route: `POST /income/verification/taxforms/get`
- Mode: WRITE
- Summary: (Deprecated) Retrieve information from the tax documents used for income verification
- Body: JSON request body accepted.
### income_verification_precheck
- Operation ID: `income_verification_precheck`
- Route: `POST /income/verification/precheck`
- Mode: WRITE
- Summary: (Deprecated) Check digital income verification eligibility and optimize conversion
- Body: JSON request body accepted.

View File

@@ -0,0 +1,38 @@
---
name: institutions-routes
description: Handle 3 OpenAPI operation(s) under /institutions for the institutions route group.
---
# institutions API Routes
Handle 3 OpenAPI operation(s) under /institutions for the institutions route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### institutions_get
- Operation ID: `institutions_get`
- Route: `POST /institutions/get`
- Mode: WRITE
- Summary: Get details of all supported institutions
- Body: JSON request body accepted.
### institutions_search
- Operation ID: `institutions_search`
- Route: `POST /institutions/search`
- Mode: WRITE
- Summary: Search institutions
- Body: JSON request body accepted.
### institutions_get_by_id
- Operation ID: `institutions_get_by_id`
- Route: `POST /institutions/get_by_id`
- Mode: WRITE
- Summary: Get details of an institution
- Body: JSON request body accepted.

View File

@@ -0,0 +1,46 @@
---
name: investments-routes
description: Handle 4 OpenAPI operation(s) under /investments for the investments route group.
---
# investments API Routes
Handle 4 OpenAPI operation(s) under /investments for the investments route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### investments_holdings_get
- Operation ID: `investments_holdings_get`
- Route: `POST /investments/holdings/get`
- Mode: WRITE
- Summary: Get Investment holdings
- Body: JSON request body accepted.
### investments_transactions_get
- Operation ID: `investments_transactions_get`
- Route: `POST /investments/transactions/get`
- Mode: WRITE
- Summary: Get investment transactions
- Body: JSON request body accepted.
### investments_refresh
- Operation ID: `investments_refresh`
- Route: `POST /investments/refresh`
- Mode: WRITE
- Summary: Refresh investment data
- Body: JSON request body accepted.
### investments_auth_get
- Operation ID: `investments_auth_get`
- Route: `POST /investments/auth/get`
- Mode: WRITE
- Summary: Get data needed to authorize an investments transfer
- Body: JSON request body accepted.

38
skills/issues/SKILL.md Normal file
View File

@@ -0,0 +1,38 @@
---
name: issues-routes
description: Handle 3 OpenAPI operation(s) under /issues for the issues route group.
---
# issues API Routes
Handle 3 OpenAPI operation(s) under /issues for the issues route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### issues_search
- Operation ID: `issues_search`
- Route: `POST /issues/search`
- Mode: WRITE
- Summary: Search for an Issue
- Body: JSON request body accepted.
### issues_get
- Operation ID: `issues_get`
- Route: `POST /issues/get`
- Mode: WRITE
- Summary: Get an Issue
- Body: JSON request body accepted.
### issues_subscribe
- Operation ID: `issues_subscribe`
- Route: `POST /issues/subscribe`
- Mode: WRITE
- Summary: Subscribe to an Issue
- Body: JSON request body accepted.

110
skills/item/SKILL.md Normal file
View File

@@ -0,0 +1,110 @@
---
name: item-routes
description: Handle 12 OpenAPI operation(s) under /item for the item route group.
---
# item API Routes
Handle 12 OpenAPI operation(s) under /item for the item route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### item_activity_list
- Operation ID: `item_activity_list`
- Route: `POST /item/activity/list`
- Mode: WRITE
- Summary: List a historical log of user consent events
- Body: JSON request body accepted.
### item_application_list
- Operation ID: `item_application_list`
- Route: `POST /item/application/list`
- Mode: WRITE
- Summary: List a user's connected applications
- Body: JSON request body accepted.
### item_application_unlink
- Operation ID: `item_application_unlink`
- Route: `POST /item/application/unlink`
- Mode: WRITE
- Summary: Unlink a user's connected application
- Body: JSON request body accepted.
### item_application_scopes_update
- Operation ID: `item_application_scopes_update`
- Route: `POST /item/application/scopes/update`
- Mode: WRITE
- Summary: Update the scopes of access for a particular application
- Body: JSON request body accepted.
### item_get
- Operation ID: `item_get`
- Route: `POST /item/get`
- Mode: WRITE
- Summary: Retrieve an Item
- Body: JSON request body accepted.
### item_remove
- Operation ID: `item_remove`
- Route: `POST /item/remove`
- Mode: WRITE
- Summary: Remove an Item
- Body: JSON request body accepted.
### item_products_terminate
- Operation ID: `item_products_terminate`
- Route: `POST /item/products/terminate`
- Mode: WRITE
- Summary: Terminate products for an Item
- Body: JSON request body accepted.
### item_webhook_update
- Operation ID: `item_webhook_update`
- Route: `POST /item/webhook/update`
- Mode: WRITE
- Summary: Update Webhook URL
- Body: JSON request body accepted.
### item_access_token_invalidate
- Operation ID: `item_access_token_invalidate`
- Route: `POST /item/access_token/invalidate`
- Mode: WRITE
- Summary: Invalidate access_token
- Body: JSON request body accepted.
### item_public_token_exchange
- Operation ID: `item_public_token_exchange`
- Route: `POST /item/public_token/exchange`
- Mode: WRITE
- Summary: Exchange public token for an access token
- Body: JSON request body accepted.
### item_create_public_token
- Operation ID: `item_create_public_token`
- Route: `POST /item/public_token/create`
- Mode: WRITE
- Summary: Create public token
- Body: JSON request body accepted.
### item_import
- Operation ID: `item_import`
- Route: `POST /item/import`
- Mode: WRITE
- Summary: Import Item
- Body: JSON request body accepted.

View File

@@ -0,0 +1,22 @@
---
name: liabilities-routes
description: Handle 1 OpenAPI operation(s) under /liabilities/get for the liabilities route group.
---
# liabilities API Routes
Handle 1 OpenAPI operation(s) under /liabilities/get for the liabilities route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### liabilities_get
- Operation ID: `liabilities_get`
- Route: `POST /liabilities/get`
- Mode: WRITE
- Summary: Retrieve Liabilities data
- Body: JSON request body accepted.

View File

@@ -0,0 +1,30 @@
---
name: link-delivery-routes
description: Handle 2 OpenAPI operation(s) under /link_delivery for the link delivery route group.
---
# link delivery API Routes
Handle 2 OpenAPI operation(s) under /link_delivery for the link delivery route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### link_delivery_create
- Operation ID: `link_delivery_create`
- Route: `POST /link_delivery/create`
- Mode: WRITE
- Summary: Create Hosted Link session
- Body: JSON request body accepted.
### link_delivery_get
- Operation ID: `link_delivery_get`
- Route: `POST /link_delivery/get`
- Mode: WRITE
- Summary: Get Hosted Link session
- Body: JSON request body accepted.

38
skills/link/SKILL.md Normal file
View File

@@ -0,0 +1,38 @@
---
name: link-routes
description: Handle 3 OpenAPI operation(s) under /link for the link route group.
---
# link API Routes
Handle 3 OpenAPI operation(s) under /link for the link route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### link_token_create
- Operation ID: `link_token_create`
- Route: `POST /link/token/create`
- Mode: WRITE
- Summary: Create Link Token
- Body: JSON request body accepted.
### link_token_get
- Operation ID: `link_token_get`
- Route: `POST /link/token/get`
- Mode: WRITE
- Summary: Get Link Token
- Body: JSON request body accepted.
### link_oauth_correlation_id_exchange
- Operation ID: `link_oauth_correlation_id_exchange`
- Route: `POST /link/oauth/correlation_id/exchange`
- Mode: WRITE
- Summary: Exchange the Link Correlation ID for a Link Token
- Body: JSON request body accepted.

22
skills/network/SKILL.md Normal file
View File

@@ -0,0 +1,22 @@
---
name: network-routes
description: Handle 1 OpenAPI operation(s) under /network/status/get for the network route group.
---
# network API Routes
Handle 1 OpenAPI operation(s) under /network/status/get for the network route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### network_status_get
- Operation ID: `network_status_get`
- Route: `POST /network/status/get`
- Mode: WRITE
- Summary: Check a user's Plaid Network status
- Body: JSON request body accepted.

38
skills/oauth/SKILL.md Normal file
View File

@@ -0,0 +1,38 @@
---
name: oauth-routes
description: Handle 3 OpenAPI operation(s) under /oauth for the oauth route group.
---
# oauth API Routes
Handle 3 OpenAPI operation(s) under /oauth for the oauth route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### oauth_token
- Operation ID: `oauth_token`
- Route: `POST /oauth/token`
- Mode: WRITE
- Summary: Create or refresh an OAuth access token
- Body: JSON request body accepted.
### oauth_introspect
- Operation ID: `oauth_introspect`
- Route: `POST /oauth/introspect`
- Mode: WRITE
- Summary: Get metadata about an OAuth token
- Body: JSON request body accepted.
### oauth_revoke
- Operation ID: `oauth_revoke`
- Route: `POST /oauth/revoke`
- Mode: WRITE
- Summary: Revoke an OAuth token
- Body: JSON request body accepted.

54
skills/partner/SKILL.md Normal file
View File

@@ -0,0 +1,54 @@
---
name: partner-routes
description: Handle 5 OpenAPI operation(s) under /partner/customer for the partner route group.
---
# partner API Routes
Handle 5 OpenAPI operation(s) under /partner/customer for the partner route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### partner_customer_create
- Operation ID: `partner_customer_create`
- Route: `POST /partner/customer/create`
- Mode: WRITE
- Summary: Creates a new end customer for a Plaid reseller.
- Body: JSON request body accepted.
### partner_customer_get
- Operation ID: `partner_customer_get`
- Route: `POST /partner/customer/get`
- Mode: WRITE
- Summary: Returns a Plaid reseller's end customer.
- Body: JSON request body accepted.
### partner_customer_enable
- Operation ID: `partner_customer_enable`
- Route: `POST /partner/customer/enable`
- Mode: WRITE
- Summary: Enables a Plaid reseller's end customer in the Production environment.
- Body: JSON request body accepted.
### partner_customer_remove
- Operation ID: `partner_customer_remove`
- Route: `POST /partner/customer/remove`
- Mode: WRITE
- Summary: Removes a Plaid reseller's end customer.
- Body: JSON request body accepted.
### partner_customer_oauth_institutions_get
- Operation ID: `partner_customer_oauth_institutions_get`
- Route: `POST /partner/customer/oauth_institutions/get`
- Mode: WRITE
- Summary: Returns OAuth-institution registration information for a given end customer.
- Body: JSON request body accepted.

View File

@@ -0,0 +1,110 @@
---
name: payment-initiation-routes
description: Handle 12 OpenAPI operation(s) under /payment_initiation for the payment initiation route group.
---
# payment initiation API Routes
Handle 12 OpenAPI operation(s) under /payment_initiation for the payment initiation route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### payment_initiation_recipient_create
- Operation ID: `payment_initiation_recipient_create`
- Route: `POST /payment_initiation/recipient/create`
- Mode: WRITE
- Summary: Create payment recipient
- Body: JSON request body accepted.
### payment_initiation_payment_reverse
- Operation ID: `payment_initiation_payment_reverse`
- Route: `POST /payment_initiation/payment/reverse`
- Mode: WRITE
- Summary: Reverse an existing payment
- Body: JSON request body accepted.
### payment_initiation_recipient_get
- Operation ID: `payment_initiation_recipient_get`
- Route: `POST /payment_initiation/recipient/get`
- Mode: WRITE
- Summary: Get payment recipient
- Body: JSON request body accepted.
### payment_initiation_recipient_list
- Operation ID: `payment_initiation_recipient_list`
- Route: `POST /payment_initiation/recipient/list`
- Mode: WRITE
- Summary: List payment recipients
- Body: JSON request body accepted.
### payment_initiation_payment_create
- Operation ID: `payment_initiation_payment_create`
- Route: `POST /payment_initiation/payment/create`
- Mode: WRITE
- Summary: Create a payment
- Body: JSON request body accepted.
### create_payment_token
- Operation ID: `create_payment_token`
- Route: `POST /payment_initiation/payment/token/create`
- Mode: WRITE
- Summary: Create payment token
- Body: JSON request body accepted.
### payment_initiation_consent_create
- Operation ID: `payment_initiation_consent_create`
- Route: `POST /payment_initiation/consent/create`
- Mode: WRITE
- Summary: Create payment consent
- Body: JSON request body accepted.
### payment_initiation_consent_get
- Operation ID: `payment_initiation_consent_get`
- Route: `POST /payment_initiation/consent/get`
- Mode: WRITE
- Summary: Get payment consent
- Body: JSON request body accepted.
### payment_initiation_consent_revoke
- Operation ID: `payment_initiation_consent_revoke`
- Route: `POST /payment_initiation/consent/revoke`
- Mode: WRITE
- Summary: Revoke payment consent
- Body: JSON request body accepted.
### payment_initiation_consent_payment_execute
- Operation ID: `payment_initiation_consent_payment_execute`
- Route: `POST /payment_initiation/consent/payment/execute`
- Mode: WRITE
- Summary: Execute a single payment using consent
- Body: JSON request body accepted.
### payment_initiation_payment_get
- Operation ID: `payment_initiation_payment_get`
- Route: `POST /payment_initiation/payment/get`
- Mode: WRITE
- Summary: Get payment details
- Body: JSON request body accepted.
### payment_initiation_payment_list
- Operation ID: `payment_initiation_payment_list`
- Route: `POST /payment_initiation/payment/list`
- Mode: WRITE
- Summary: List payments
- Body: JSON request body accepted.

View File

@@ -0,0 +1,38 @@
---
name: payment-profile-routes
description: Handle 3 OpenAPI operation(s) under /payment_profile for the payment profile route group.
---
# payment profile API Routes
Handle 3 OpenAPI operation(s) under /payment_profile for the payment profile route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### payment_profile_create
- Operation ID: `payment_profile_create`
- Route: `POST /payment_profile/create`
- Mode: WRITE
- Summary: Create payment profile
- Body: JSON request body accepted.
### payment_profile_get
- Operation ID: `payment_profile_get`
- Route: `POST /payment_profile/get`
- Mode: WRITE
- Summary: Get payment profile
- Body: JSON request body accepted.
### payment_profile_remove
- Operation ID: `payment_profile_remove`
- Route: `POST /payment_profile/remove`
- Mode: WRITE
- Summary: Remove payment profile
- Body: JSON request body accepted.

206
skills/processor/SKILL.md Normal file
View File

@@ -0,0 +1,206 @@
---
name: processor-routes
description: Handle 24 OpenAPI operation(s) under /processor for the processor route group.
---
# processor API Routes
Handle 24 OpenAPI operation(s) under /processor for the processor route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### processor_auth_get
- Operation ID: `processor_auth_get`
- Route: `POST /processor/auth/get`
- Mode: WRITE
- Summary: Retrieve Auth data
- Body: JSON request body accepted.
### processor_account_get
- Operation ID: `processor_account_get`
- Route: `POST /processor/account/get`
- Mode: WRITE
- Summary: Retrieve the account associated with a processor token
- Body: JSON request body accepted.
### processor_investments_holdings_get
- Operation ID: `processor_investments_holdings_get`
- Route: `POST /processor/investments/holdings/get`
- Mode: WRITE
- Summary: Retrieve Investment Holdings
- Body: JSON request body accepted.
### processor_investments_auth_get
- Operation ID: `processor_investments_auth_get`
- Route: `POST /processor/investments/auth/get`
- Mode: WRITE
- Summary: Get investment account authentication data
- Body: JSON request body accepted.
### processor_investments_transactions_get
- Operation ID: `processor_investments_transactions_get`
- Route: `POST /processor/investments/transactions/get`
- Mode: WRITE
- Summary: Get investment transactions data
- Body: JSON request body accepted.
### processor_transactions_get
- Operation ID: `processor_transactions_get`
- Route: `POST /processor/transactions/get`
- Mode: WRITE
- Summary: Get transaction data
- Body: JSON request body accepted.
### processor_transactions_sync
- Operation ID: `processor_transactions_sync`
- Route: `POST /processor/transactions/sync`
- Mode: WRITE
- Summary: Get incremental transaction updates on a processor token
- Body: JSON request body accepted.
### processor_transactions_refresh
- Operation ID: `processor_transactions_refresh`
- Route: `POST /processor/transactions/refresh`
- Mode: WRITE
- Summary: Refresh transaction data
- Body: JSON request body accepted.
### processor_transactions_recurring_get
- Operation ID: `processor_transactions_recurring_get`
- Route: `POST /processor/transactions/recurring/get`
- Mode: WRITE
- Summary: Fetch recurring transaction streams
- Body: JSON request body accepted.
### processor_signal_evaluate
- Operation ID: `processor_signal_evaluate`
- Route: `POST /processor/signal/evaluate`
- Mode: WRITE
- Summary: Evaluate a planned ACH transaction
- Body: JSON request body accepted.
### processor_signal_decision_report
- Operation ID: `processor_signal_decision_report`
- Route: `POST /processor/signal/decision/report`
- Mode: WRITE
- Summary: Report whether you initiated an ACH transaction
- Body: JSON request body accepted.
### processor_signal_return_report
- Operation ID: `processor_signal_return_report`
- Route: `POST /processor/signal/return/report`
- Mode: WRITE
- Summary: Report a return for an ACH transaction
- Body: JSON request body accepted.
### processor_signal_prepare
- Operation ID: `processor_signal_prepare`
- Route: `POST /processor/signal/prepare`
- Mode: WRITE
- Summary: Opt-in a processor token to Signal
- Body: JSON request body accepted.
### processor_bank_transfer_create
- Operation ID: `processor_bank_transfer_create`
- Route: `POST /processor/bank_transfer/create`
- Mode: WRITE
- Summary: Create a bank transfer as a processor
- Body: JSON request body accepted.
### processor_liabilities_get
- Operation ID: `processor_liabilities_get`
- Route: `POST /processor/liabilities/get`
- Mode: WRITE
- Summary: Retrieve Liabilities data
- Body: JSON request body accepted.
### processor_identity_get
- Operation ID: `processor_identity_get`
- Route: `POST /processor/identity/get`
- Mode: WRITE
- Summary: Retrieve Identity data
- Body: JSON request body accepted.
### processor_identity_match
- Operation ID: `processor_identity_match`
- Route: `POST /processor/identity/match`
- Mode: WRITE
- Summary: Retrieve identity match score
- Body: JSON request body accepted.
### processor_balance_get
- Operation ID: `processor_balance_get`
- Route: `POST /processor/balance/get`
- Mode: WRITE
- Summary: Retrieve Balance data
- Body: JSON request body accepted.
### processor_token_create
- Operation ID: `processor_token_create`
- Route: `POST /processor/token/create`
- Mode: WRITE
- Summary: Create processor token
- Body: JSON request body accepted.
### processor_token_permissions_set
- Operation ID: `processor_token_permissions_set`
- Route: `POST /processor/token/permissions/set`
- Mode: WRITE
- Summary: Control a processor's access to products
- Body: JSON request body accepted.
### processor_token_permissions_get
- Operation ID: `processor_token_permissions_get`
- Route: `POST /processor/token/permissions/get`
- Mode: WRITE
- Summary: Get a processor token's product permissions
- Body: JSON request body accepted.
### processor_token_webhook_update
- Operation ID: `processor_token_webhook_update`
- Route: `POST /processor/token/webhook/update`
- Mode: WRITE
- Summary: Update a processor token's webhook URL
- Body: JSON request body accepted.
### processor_stripe_bank_account_token_create
- Operation ID: `processor_stripe_bank_account_token_create`
- Route: `POST /processor/stripe/bank_account_token/create`
- Mode: WRITE
- Summary: Create Stripe bank account token
- Body: JSON request body accepted.
### processor_apex_processor_token_create
- Operation ID: `processor_apex_processor_token_create`
- Route: `POST /processor/apex/processor_token/create`
- Mode: WRITE
- Summary: Create Apex bank account token
- Body: JSON request body accepted.

22
skills/profile/SKILL.md Normal file
View File

@@ -0,0 +1,22 @@
---
name: profile-routes
description: Handle 1 OpenAPI operation(s) under /profile/network_status/get for the profile route group.
---
# profile API Routes
Handle 1 OpenAPI operation(s) under /profile/network_status/get for the profile route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### profile_network_status_get
- Operation ID: `profile_network_status_get`
- Route: `POST /profile/network_status/get`
- Mode: WRITE
- Summary: Check a user's Plaid Network status
- Body: JSON request body accepted.

54
skills/protect/SKILL.md Normal file
View File

@@ -0,0 +1,54 @@
---
name: protect-routes
description: Handle 5 OpenAPI operation(s) under /protect for the protect route group.
---
# protect API Routes
Handle 5 OpenAPI operation(s) under /protect for the protect route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### protect_user_insights_get
- Operation ID: `protect_user_insights_get`
- Route: `POST /protect/user/insights/get`
- Mode: WRITE
- Summary: Get Protect user insights
- Body: JSON request body accepted.
### protect_report_create
- Operation ID: `protect_report_create`
- Route: `POST /protect/report/create`
- Mode: WRITE
- Summary: Create a Protect report
- Body: JSON request body accepted.
### protect_compute
- Operation ID: `protect_compute`
- Route: `POST /protect/compute`
- Mode: WRITE
- Summary: Compute Protect Trust Index scores and subscores
- Body: JSON request body accepted.
### protect_event_send
- Operation ID: `protect_event_send`
- Route: `POST /protect/event/send`
- Mode: WRITE
- Summary: Send a new event to enrich user data
- Body: JSON request body accepted.
### protect_event_get
- Operation ID: `protect_event_get`
- Route: `POST /protect/event/get`
- Mode: WRITE
- Summary: Get information about a user event
- Body: JSON request body accepted.

238
skills/sandbox/SKILL.md Normal file
View File

@@ -0,0 +1,238 @@
---
name: sandbox-routes
description: Handle 28 OpenAPI operation(s) under /sandbox for the sandbox route group.
---
# sandbox API Routes
Handle 28 OpenAPI operation(s) under /sandbox for the sandbox route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### sandbox_transactions_create
- Operation ID: `sandbox_transactions_create`
- Route: `POST /sandbox/transactions/create`
- Mode: WRITE
- Summary: Create sandbox transactions
- Body: JSON request body accepted.
### sandbox_processor_token_create
- Operation ID: `sandbox_processor_token_create`
- Route: `POST /sandbox/processor_token/create`
- Mode: WRITE
- Summary: Create a test Item and processor token
- Body: JSON request body accepted.
### sandbox_public_token_create
- Operation ID: `sandbox_public_token_create`
- Route: `POST /sandbox/public_token/create`
- Mode: WRITE
- Summary: Create a test Item
- Body: JSON request body accepted.
### sandbox_item_fire_webhook
- Operation ID: `sandbox_item_fire_webhook`
- Route: `POST /sandbox/item/fire_webhook`
- Mode: WRITE
- Summary: Fire a test webhook
- Body: JSON request body accepted.
### sandbox_item_reset_login
- Operation ID: `sandbox_item_reset_login`
- Route: `POST /sandbox/item/reset_login`
- Mode: WRITE
- Summary: Force a Sandbox Item into an error state
- Body: JSON request body accepted.
### sandbox_item_application_seed
- Operation ID: `sandbox_item_application_seed`
- Route: `POST /sandbox/item/application/seed`
- Mode: WRITE
- Summary: Seed a connected application for a Permissions Manager sandbox item
- Body: JSON request body accepted.
### sandbox_item_set_verification_status
- Operation ID: `sandbox_item_set_verification_status`
- Route: `POST /sandbox/item/set_verification_status`
- Mode: WRITE
- Summary: Set verification status for Sandbox account
- Body: JSON request body accepted.
### sandbox_user_reset_login
- Operation ID: `sandbox_user_reset_login`
- Route: `POST /sandbox/user/reset_login`
- Mode: WRITE
- Summary: Force item(s) for a Sandbox User into an error state
- Body: JSON request body accepted.
### sandbox_bank_transfer_simulate
- Operation ID: `sandbox_bank_transfer_simulate`
- Route: `POST /sandbox/bank_transfer/simulate`
- Mode: WRITE
- Summary: Simulate a bank transfer event in Sandbox
- Body: JSON request body accepted.
### sandbox_transfer_sweep_simulate
- Operation ID: `sandbox_transfer_sweep_simulate`
- Route: `POST /sandbox/transfer/sweep/simulate`
- Mode: WRITE
- Summary: Simulate creating a sweep
- Body: JSON request body accepted.
### sandbox_transfer_simulate
- Operation ID: `sandbox_transfer_simulate`
- Route: `POST /sandbox/transfer/simulate`
- Mode: WRITE
- Summary: Simulate a transfer event in Sandbox
- Body: JSON request body accepted.
### sandbox_transfer_refund_simulate
- Operation ID: `sandbox_transfer_refund_simulate`
- Route: `POST /sandbox/transfer/refund/simulate`
- Mode: WRITE
- Summary: Simulate a refund event in Sandbox
- Body: JSON request body accepted.
### sandbox_transfer_ledger_simulate_available
- Operation ID: `sandbox_transfer_ledger_simulate_available`
- Route: `POST /sandbox/transfer/ledger/simulate_available`
- Mode: WRITE
- Summary: Simulate converting pending balance to available balance
- Body: JSON request body accepted.
### sandbox_transfer_ledger_deposit_simulate
- Operation ID: `sandbox_transfer_ledger_deposit_simulate`
- Route: `POST /sandbox/transfer/ledger/deposit/simulate`
- Mode: WRITE
- Summary: Simulate a ledger deposit event in Sandbox
- Body: JSON request body accepted.
### sandbox_transfer_ledger_withdraw_simulate
- Operation ID: `sandbox_transfer_ledger_withdraw_simulate`
- Route: `POST /sandbox/transfer/ledger/withdraw/simulate`
- Mode: WRITE
- Summary: Simulate a ledger withdraw event in Sandbox
- Body: JSON request body accepted.
### sandbox_transfer_repayment_simulate
- Operation ID: `sandbox_transfer_repayment_simulate`
- Route: `POST /sandbox/transfer/repayment/simulate`
- Mode: WRITE
- Summary: Trigger the creation of a repayment
- Body: JSON request body accepted.
### sandbox_transfer_fire_webhook
- Operation ID: `sandbox_transfer_fire_webhook`
- Route: `POST /sandbox/transfer/fire_webhook`
- Mode: WRITE
- Summary: Manually fire a Transfer webhook
- Body: JSON request body accepted.
### sandbox_transfer_test_clock_create
- Operation ID: `sandbox_transfer_test_clock_create`
- Route: `POST /sandbox/transfer/test_clock/create`
- Mode: WRITE
- Summary: Create a test clock
- Body: JSON request body accepted.
### sandbox_transfer_test_clock_advance
- Operation ID: `sandbox_transfer_test_clock_advance`
- Route: `POST /sandbox/transfer/test_clock/advance`
- Mode: WRITE
- Summary: Advance a test clock
- Body: JSON request body accepted.
### sandbox_transfer_test_clock_get
- Operation ID: `sandbox_transfer_test_clock_get`
- Route: `POST /sandbox/transfer/test_clock/get`
- Mode: WRITE
- Summary: Get a test clock
- Body: JSON request body accepted.
### sandbox_transfer_test_clock_list
- Operation ID: `sandbox_transfer_test_clock_list`
- Route: `POST /sandbox/transfer/test_clock/list`
- Mode: WRITE
- Summary: List test clocks
- Body: JSON request body accepted.
### sandbox_payment_profile_reset_login
- Operation ID: `sandbox_payment_profile_reset_login`
- Route: `POST /sandbox/payment_profile/reset_login`
- Mode: WRITE
- Summary: Reset the login of a Payment Profile
- Body: JSON request body accepted.
### sandbox_payment_simulate
- Operation ID: `sandbox_payment_simulate`
- Route: `POST /sandbox/payment/simulate`
- Mode: WRITE
- Summary: Simulate a payment event in Sandbox
- Body: JSON request body accepted.
### sandbox_bank_transfer_fire_webhook
- Operation ID: `sandbox_bank_transfer_fire_webhook`
- Route: `POST /sandbox/bank_transfer/fire_webhook`
- Mode: WRITE
- Summary: Manually fire a Bank Transfer webhook
- Body: JSON request body accepted.
### sandbox_income_fire_webhook
- Operation ID: `sandbox_income_fire_webhook`
- Route: `POST /sandbox/income/fire_webhook`
- Mode: WRITE
- Summary: Manually fire an Income webhook
- Body: JSON request body accepted.
### sandbox_bank_income_fire_webhook
- Operation ID: `sandbox_bank_income_fire_webhook`
- Route: `POST /sandbox/bank_income/fire_webhook`
- Mode: WRITE
- Summary: Manually fire a Bank Income webhook in Sandbox
- Body: JSON request body accepted.
### sandbox_cra_cashflow_updates_update
- Operation ID: `sandbox_cra_cashflow_updates_update`
- Route: `POST /sandbox/cra/cashflow_updates/update`
- Mode: WRITE
- Summary: Trigger an update for Cash Flow Updates
- Body: JSON request body accepted.
### sandbox_oauth_select_accounts
- Operation ID: `sandbox_oauth_select_accounts`
- Route: `POST /sandbox/oauth/select_accounts`
- Mode: WRITE
- Summary: Save the selected accounts when connecting to the Platypus OAuth institution
- Body: JSON request body accepted.

22
skills/session/SKILL.md Normal file
View File

@@ -0,0 +1,22 @@
---
name: session-routes
description: Handle 1 OpenAPI operation(s) under /session/token/create for the session route group.
---
# session API Routes
Handle 1 OpenAPI operation(s) under /session/token/create for the session route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### session_token_create
- Operation ID: `session_token_create`
- Route: `POST /session/token/create`
- Mode: WRITE
- Summary: Create a Link token for Layer
- Body: JSON request body accepted.

54
skills/signal/SKILL.md Normal file
View File

@@ -0,0 +1,54 @@
---
name: signal-routes
description: Handle 5 OpenAPI operation(s) under /signal for the signal route group.
---
# signal API Routes
Handle 5 OpenAPI operation(s) under /signal for the signal route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### signal_evaluate
- Operation ID: `signal_evaluate`
- Route: `POST /signal/evaluate`
- Mode: WRITE
- Summary: Evaluate a planned ACH transaction
- Body: JSON request body accepted.
### signal_schedule
- Operation ID: `signal_schedule`
- Route: `POST /signal/schedule`
- Mode: WRITE
- Summary: Schedule a planned ACH transaction
- Body: JSON request body accepted.
### signal_decision_report
- Operation ID: `signal_decision_report`
- Route: `POST /signal/decision/report`
- Mode: WRITE
- Summary: Report whether you initiated an ACH transaction
- Body: JSON request body accepted.
### signal_return_report
- Operation ID: `signal_return_report`
- Route: `POST /signal/return/report`
- Mode: WRITE
- Summary: Report a return for an ACH transaction
- Body: JSON request body accepted.
### signal_prepare
- Operation ID: `signal_prepare`
- Route: `POST /signal/prepare`
- Mode: WRITE
- Summary: Opt-in an Item to Signal Transaction Scores
- Body: JSON request body accepted.

View File

@@ -0,0 +1,38 @@
---
name: statements-routes
description: Handle 3 OpenAPI operation(s) under /statements for the statements route group.
---
# statements API Routes
Handle 3 OpenAPI operation(s) under /statements for the statements route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### statements_list
- Operation ID: `statements_list`
- Route: `POST /statements/list`
- Mode: WRITE
- Summary: Retrieve a list of all statements associated with an Item.
- Body: JSON request body accepted.
### statements_download
- Operation ID: `statements_download`
- Route: `POST /statements/download`
- Mode: WRITE
- Summary: Retrieve a single statement.
- Body: JSON request body accepted.
### statements_refresh
- Operation ID: `statements_refresh`
- Route: `POST /statements/refresh`
- Mode: WRITE
- Summary: Refresh statements data.
- Body: JSON request body accepted.

View File

@@ -0,0 +1,54 @@
---
name: transactions-routes
description: Handle 5 OpenAPI operation(s) under /transactions for the transactions route group.
---
# transactions API Routes
Handle 5 OpenAPI operation(s) under /transactions for the transactions route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### transactions_get
- Operation ID: `transactions_get`
- Route: `POST /transactions/get`
- Mode: WRITE
- Summary: Get transaction data
- Body: JSON request body accepted.
### transactions_refresh
- Operation ID: `transactions_refresh`
- Route: `POST /transactions/refresh`
- Mode: WRITE
- Summary: Refresh transaction data
- Body: JSON request body accepted.
### transactions_recurring_get
- Operation ID: `transactions_recurring_get`
- Route: `POST /transactions/recurring/get`
- Mode: WRITE
- Summary: Fetch recurring transaction streams
- Body: JSON request body accepted.
### transactions_sync
- Operation ID: `transactions_sync`
- Route: `POST /transactions/sync`
- Mode: WRITE
- Summary: Get incremental transaction updates on an Item
- Body: JSON request body accepted.
### transactions_enrich
- Operation ID: `transactions_enrich`
- Route: `POST /transactions/enrich`
- Mode: WRITE
- Summary: Enrich locally-held transaction data
- Body: JSON request body accepted.

350
skills/transfer/SKILL.md Normal file
View File

@@ -0,0 +1,350 @@
---
name: transfer-routes
description: Handle 42 OpenAPI operation(s) under /transfer for the transfer route group.
---
# transfer API Routes
Handle 42 OpenAPI operation(s) under /transfer for the transfer route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### transfer_get
- Operation ID: `transfer_get`
- Route: `POST /transfer/get`
- Mode: WRITE
- Summary: Retrieve a transfer
- Body: JSON request body accepted.
### transfer_recurring_get
- Operation ID: `transfer_recurring_get`
- Route: `POST /transfer/recurring/get`
- Mode: WRITE
- Summary: Retrieve a recurring transfer
- Body: JSON request body accepted.
### transfer_authorization_create
- Operation ID: `transfer_authorization_create`
- Route: `POST /transfer/authorization/create`
- Mode: WRITE
- Summary: Create a transfer authorization
- Body: JSON request body accepted.
### transfer_authorization_cancel
- Operation ID: `transfer_authorization_cancel`
- Route: `POST /transfer/authorization/cancel`
- Mode: WRITE
- Summary: Cancel a transfer authorization
- Body: JSON request body accepted.
### transfer_balance_get
- Operation ID: `transfer_balance_get`
- Route: `POST /transfer/balance/get`
- Mode: WRITE
- Summary: (Deprecated) Retrieve a balance held with Plaid
- Body: JSON request body accepted.
### transfer_capabilities_get
- Operation ID: `transfer_capabilities_get`
- Route: `POST /transfer/capabilities/get`
- Mode: WRITE
- Summary: Get RTP eligibility information of a transfer
- Body: JSON request body accepted.
### transfer_configuration_get
- Operation ID: `transfer_configuration_get`
- Route: `POST /transfer/configuration/get`
- Mode: WRITE
- Summary: Get transfer product configuration
- Body: JSON request body accepted.
### transfer_ledger_get
- Operation ID: `transfer_ledger_get`
- Route: `POST /transfer/ledger/get`
- Mode: WRITE
- Summary: Retrieve Plaid Ledger balance
- Body: JSON request body accepted.
### transfer_ledger_distribute
- Operation ID: `transfer_ledger_distribute`
- Route: `POST /transfer/ledger/distribute`
- Mode: WRITE
- Summary: Move available balance between ledgers
- Body: JSON request body accepted.
### transfer_ledger_deposit
- Operation ID: `transfer_ledger_deposit`
- Route: `POST /transfer/ledger/deposit`
- Mode: WRITE
- Summary: Deposit funds into a Plaid Ledger balance
- Body: JSON request body accepted.
### transfer_ledger_withdraw
- Operation ID: `transfer_ledger_withdraw`
- Route: `POST /transfer/ledger/withdraw`
- Mode: WRITE
- Summary: Withdraw funds from a Plaid Ledger balance
- Body: JSON request body accepted.
### transfer_originator_funding_account_update
- Operation ID: `transfer_originator_funding_account_update`
- Route: `POST /transfer/originator/funding_account/update`
- Mode: WRITE
- Summary: Update the funding account associated with the originator
- Body: JSON request body accepted.
### transfer_originator_funding_account_create
- Operation ID: `transfer_originator_funding_account_create`
- Route: `POST /transfer/originator/funding_account/create`
- Mode: WRITE
- Summary: Create a new funding account for an originator
- Body: JSON request body accepted.
### transfer_metrics_get
- Operation ID: `transfer_metrics_get`
- Route: `POST /transfer/metrics/get`
- Mode: WRITE
- Summary: Get transfer product usage metrics
- Body: JSON request body accepted.
### transfer_create
- Operation ID: `transfer_create`
- Route: `POST /transfer/create`
- Mode: WRITE
- Summary: Create a transfer
- Body: JSON request body accepted.
### transfer_recurring_create
- Operation ID: `transfer_recurring_create`
- Route: `POST /transfer/recurring/create`
- Mode: WRITE
- Summary: Create a recurring transfer
- Body: JSON request body accepted.
### transfer_list
- Operation ID: `transfer_list`
- Route: `POST /transfer/list`
- Mode: WRITE
- Summary: List transfers
- Body: JSON request body accepted.
### transfer_recurring_list
- Operation ID: `transfer_recurring_list`
- Route: `POST /transfer/recurring/list`
- Mode: WRITE
- Summary: List recurring transfers
- Body: JSON request body accepted.
### transfer_cancel
- Operation ID: `transfer_cancel`
- Route: `POST /transfer/cancel`
- Mode: WRITE
- Summary: Cancel a transfer
- Body: JSON request body accepted.
### transfer_recurring_cancel
- Operation ID: `transfer_recurring_cancel`
- Route: `POST /transfer/recurring/cancel`
- Mode: WRITE
- Summary: Cancel a recurring transfer.
- Body: JSON request body accepted.
### transfer_event_list
- Operation ID: `transfer_event_list`
- Route: `POST /transfer/event/list`
- Mode: WRITE
- Summary: List transfer events
- Body: JSON request body accepted.
### transfer_ledger_event_list
- Operation ID: `transfer_ledger_event_list`
- Route: `POST /transfer/ledger/event/list`
- Mode: WRITE
- Summary: List transfer ledger events
- Body: JSON request body accepted.
### transfer_event_sync
- Operation ID: `transfer_event_sync`
- Route: `POST /transfer/event/sync`
- Mode: WRITE
- Summary: Sync transfer events
- Body: JSON request body accepted.
### transfer_sweep_get
- Operation ID: `transfer_sweep_get`
- Route: `POST /transfer/sweep/get`
- Mode: WRITE
- Summary: Retrieve a sweep
- Body: JSON request body accepted.
### transfer_sweep_list
- Operation ID: `transfer_sweep_list`
- Route: `POST /transfer/sweep/list`
- Mode: WRITE
- Summary: List sweeps
- Body: JSON request body accepted.
### transfer_migrate_account
- Operation ID: `transfer_migrate_account`
- Route: `POST /transfer/migrate_account`
- Mode: WRITE
- Summary: Migrate account into Transfers
- Body: JSON request body accepted.
### transfer_intent_create
- Operation ID: `transfer_intent_create`
- Route: `POST /transfer/intent/create`
- Mode: WRITE
- Summary: Create a transfer intent object to invoke the Transfer UI
- Body: JSON request body accepted.
### transfer_intent_get
- Operation ID: `transfer_intent_get`
- Route: `POST /transfer/intent/get`
- Mode: WRITE
- Summary: Retrieve more information about a transfer intent
- Body: JSON request body accepted.
### transfer_repayment_list
- Operation ID: `transfer_repayment_list`
- Route: `POST /transfer/repayment/list`
- Mode: WRITE
- Summary: Lists historical repayments
- Body: JSON request body accepted.
### transfer_repayment_return_list
- Operation ID: `transfer_repayment_return_list`
- Route: `POST /transfer/repayment/return/list`
- Mode: WRITE
- Summary: List the returns included in a repayment
- Body: JSON request body accepted.
### transfer_platform_requirement_submit
- Operation ID: `transfer_platform_requirement_submit`
- Route: `POST /transfer/platform/requirement/submit`
- Mode: WRITE
- Summary: Submit additional onboarding information on behalf of an originator
- Body: JSON request body accepted.
### transfer_originator_create
- Operation ID: `transfer_originator_create`
- Route: `POST /transfer/originator/create`
- Mode: WRITE
- Summary: Create a new originator
- Body: JSON request body accepted.
### transfer_questionnaire_create
- Operation ID: `transfer_questionnaire_create`
- Route: `POST /transfer/questionnaire/create`
- Mode: WRITE
- Summary: Generate a Plaid-hosted onboarding UI URL.
- Body: JSON request body accepted.
### transfer_diligence_submit
- Operation ID: `transfer_diligence_submit`
- Route: `POST /transfer/diligence/submit`
- Mode: WRITE
- Summary: Submit transfer diligence on behalf of the originator
- Body: JSON request body accepted.
### transfer_diligence_document_upload
- Operation ID: `transfer_diligence_document_upload`
- Route: `POST /transfer/diligence/document/upload`
- Mode: WRITE
- Summary: Upload transfer diligence document on behalf of the originator
- Body: JSON request body accepted.
### transfer_originator_get
- Operation ID: `transfer_originator_get`
- Route: `POST /transfer/originator/get`
- Mode: WRITE
- Summary: Get status of an originator's onboarding
- Body: JSON request body accepted.
### transfer_originator_list
- Operation ID: `transfer_originator_list`
- Route: `POST /transfer/originator/list`
- Mode: WRITE
- Summary: Get status of all originators' onboarding
- Body: JSON request body accepted.
### transfer_refund_create
- Operation ID: `transfer_refund_create`
- Route: `POST /transfer/refund/create`
- Mode: WRITE
- Summary: Create a refund
- Body: JSON request body accepted.
### transfer_refund_get
- Operation ID: `transfer_refund_get`
- Route: `POST /transfer/refund/get`
- Mode: WRITE
- Summary: Retrieve a refund
- Body: JSON request body accepted.
### transfer_refund_cancel
- Operation ID: `transfer_refund_cancel`
- Route: `POST /transfer/refund/cancel`
- Mode: WRITE
- Summary: Cancel a refund
- Body: JSON request body accepted.
### transfer_platform_originator_create
- Operation ID: `transfer_platform_originator_create`
- Route: `POST /transfer/platform/originator/create`
- Mode: WRITE
- Summary: Create an originator for Transfer for Platforms customers
- Body: JSON request body accepted.
### transfer_platform_person_create
- Operation ID: `transfer_platform_person_create`
- Route: `POST /transfer/platform/person/create`
- Mode: WRITE
- Summary: Create a person associated with an originator
- Body: JSON request body accepted.

View File

@@ -0,0 +1,30 @@
---
name: user-account-routes
description: Handle 2 OpenAPI operation(s) under /user_account/session for the user account route group.
---
# user account API Routes
Handle 2 OpenAPI operation(s) under /user_account/session for the user account route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### user_account_session_get
- Operation ID: `user_account_session_get`
- Route: `POST /user_account/session/get`
- Mode: WRITE
- Summary: Retrieve User Account
- Body: JSON request body accepted.
### user_account_session_event_send
- Operation ID: `user_account_session_event_send`
- Route: `POST /user_account/session/event/send`
- Mode: WRITE
- Summary: Send User Account Session Event
- Body: JSON request body accepted.

128
skills/user/SKILL.md Normal file
View File

@@ -0,0 +1,128 @@
---
name: user-routes
description: Handle 13 OpenAPI operation(s) under /user for the user route group.
---
# user API Routes
Handle 13 OpenAPI operation(s) under /user for the user route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### user_transactions_refresh
- Operation ID: `user_transactions_refresh`
- Route: `POST /user/transactions/refresh`
- Mode: WRITE
- Summary: Refresh user items for Transactions bundle
- Body: JSON request body accepted.
### user_financial_data_refresh
- Operation ID: `user_financial_data_refresh`
- Route: `POST /user/financial_data/refresh`
- Mode: WRITE
- Summary: Refresh user items for Financial-Insights bundle
- Body: JSON request body accepted.
### user_create
- Operation ID: `user_create`
- Route: `POST /user/create`
- Mode: WRITE
- Summary: Create user
- Parameters:
- `Plaid-New-User-API-Enabled` in `header`
- Body: JSON request body accepted.
### user_get
- Operation ID: `user_get`
- Route: `POST /user/get`
- Mode: WRITE
- Summary: Retrieve user identity and information
- Parameters:
- `Plaid-New-User-API-Enabled` in `header`
- Body: JSON request body accepted.
### user_identity_remove
- Operation ID: `user_identity_remove`
- Route: `POST /user/identity/remove`
- Mode: WRITE
- Summary: Remove user identity data
- Parameters:
- `Plaid-New-User-API-Enabled` in `header`
- Body: JSON request body accepted.
### user_update
- Operation ID: `user_update`
- Route: `POST /user/update`
- Mode: WRITE
- Summary: Update user information
- Parameters:
- `Plaid-New-User-API-Enabled` in `header`
- Body: JSON request body accepted.
### user_remove
- Operation ID: `user_remove`
- Route: `POST /user/remove`
- Mode: WRITE
- Summary: Remove user
- Parameters:
- `Plaid-New-User-API-Enabled` in `header`
- Body: JSON request body accepted.
### user_products_terminate
- Operation ID: `user_products_terminate`
- Route: `POST /user/products/terminate`
- Mode: WRITE
- Summary: Terminate user-based products
- Body: JSON request body accepted.
### user_items_get
- Operation ID: `user_items_get`
- Route: `POST /user/items/get`
- Mode: WRITE
- Summary: Get Items associated with a User
- Body: JSON request body accepted.
### user_items_associate
- Operation ID: `user_items_associate`
- Route: `POST /user/items/associate`
- Mode: WRITE
- Summary: Associate Items to a User
- Body: JSON request body accepted.
### user_items_remove
- Operation ID: `user_items_remove`
- Route: `POST /user/items/remove`
- Mode: WRITE
- Summary: Remove Items from a User
- Body: JSON request body accepted.
### user_third_party_token_create
- Operation ID: `user_third_party_token_create`
- Route: `POST /user/third_party_token/create`
- Mode: WRITE
- Summary: Create a third-party user token
- Body: JSON request body accepted.
### user_third_party_token_remove
- Operation ID: `user_third_party_token_remove`
- Route: `POST /user/third_party_token/remove`
- Mode: WRITE
- Summary: Remove a third-party user token
- Body: JSON request body accepted.

62
skills/wallet/SKILL.md Normal file
View File

@@ -0,0 +1,62 @@
---
name: wallet-routes
description: Handle 6 OpenAPI operation(s) under /wallet for the wallet route group.
---
# wallet API Routes
Handle 6 OpenAPI operation(s) under /wallet for the wallet route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### wallet_create
- Operation ID: `wallet_create`
- Route: `POST /wallet/create`
- Mode: WRITE
- Summary: Create an e-wallet
- Body: JSON request body accepted.
### wallet_get
- Operation ID: `wallet_get`
- Route: `POST /wallet/get`
- Mode: WRITE
- Summary: Fetch an e-wallet
- Body: JSON request body accepted.
### wallet_list
- Operation ID: `wallet_list`
- Route: `POST /wallet/list`
- Mode: WRITE
- Summary: Fetch a list of e-wallets
- Body: JSON request body accepted.
### wallet_transaction_execute
- Operation ID: `wallet_transaction_execute`
- Route: `POST /wallet/transaction/execute`
- Mode: WRITE
- Summary: Execute a transaction using an e-wallet
- Body: JSON request body accepted.
### wallet_transaction_get
- Operation ID: `wallet_transaction_get`
- Route: `POST /wallet/transaction/get`
- Mode: WRITE
- Summary: Fetch an e-wallet transaction
- Body: JSON request body accepted.
### wallet_transaction_list
- Operation ID: `wallet_transaction_list`
- Route: `POST /wallet/transaction/list`
- Mode: WRITE
- Summary: List e-wallet transactions
- Body: JSON request body accepted.

View File

@@ -0,0 +1,174 @@
---
name: watchlist-screening-routes
description: Handle 20 OpenAPI operation(s) under /watchlist_screening for the watchlist screening route group.
---
# watchlist screening API Routes
Handle 20 OpenAPI operation(s) under /watchlist_screening for the watchlist screening route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### watchlist_screening_entity_create
- Operation ID: `watchlist_screening_entity_create`
- Route: `POST /watchlist_screening/entity/create`
- Mode: WRITE
- Summary: Create a watchlist screening for an entity
- Body: JSON request body accepted.
### watchlist_screening_entity_get
- Operation ID: `watchlist_screening_entity_get`
- Route: `POST /watchlist_screening/entity/get`
- Mode: WRITE
- Summary: Get an entity screening
- Body: JSON request body accepted.
### watchlist_screening_entity_history_list
- Operation ID: `watchlist_screening_entity_history_list`
- Route: `POST /watchlist_screening/entity/history/list`
- Mode: WRITE
- Summary: List history for entity watchlist screenings
- Body: JSON request body accepted.
### watchlist_screening_entity_hit_list
- Operation ID: `watchlist_screening_entity_hit_list`
- Route: `POST /watchlist_screening/entity/hit/list`
- Mode: WRITE
- Summary: List hits for entity watchlist screenings
- Body: JSON request body accepted.
### watchlist_screening_entity_list
- Operation ID: `watchlist_screening_entity_list`
- Route: `POST /watchlist_screening/entity/list`
- Mode: WRITE
- Summary: List entity watchlist screenings
- Body: JSON request body accepted.
### watchlist_screening_entity_program_get
- Operation ID: `watchlist_screening_entity_program_get`
- Route: `POST /watchlist_screening/entity/program/get`
- Mode: WRITE
- Summary: Get entity watchlist screening program
- Body: JSON request body accepted.
### watchlist_screening_entity_program_list
- Operation ID: `watchlist_screening_entity_program_list`
- Route: `POST /watchlist_screening/entity/program/list`
- Mode: WRITE
- Summary: List entity watchlist screening programs
- Body: JSON request body accepted.
### watchlist_screening_entity_review_create
- Operation ID: `watchlist_screening_entity_review_create`
- Route: `POST /watchlist_screening/entity/review/create`
- Mode: WRITE
- Summary: Create a review for an entity watchlist screening
- Body: JSON request body accepted.
### watchlist_screening_entity_review_list
- Operation ID: `watchlist_screening_entity_review_list`
- Route: `POST /watchlist_screening/entity/review/list`
- Mode: WRITE
- Summary: List reviews for entity watchlist screenings
- Body: JSON request body accepted.
### watchlist_screening_entity_update
- Operation ID: `watchlist_screening_entity_update`
- Route: `POST /watchlist_screening/entity/update`
- Mode: WRITE
- Summary: Update an entity screening
- Body: JSON request body accepted.
### watchlist_screening_individual_create
- Operation ID: `watchlist_screening_individual_create`
- Route: `POST /watchlist_screening/individual/create`
- Mode: WRITE
- Summary: Create a watchlist screening for a person
- Body: JSON request body accepted.
### watchlist_screening_individual_get
- Operation ID: `watchlist_screening_individual_get`
- Route: `POST /watchlist_screening/individual/get`
- Mode: WRITE
- Summary: Retrieve an individual watchlist screening
- Body: JSON request body accepted.
### watchlist_screening_individual_history_list
- Operation ID: `watchlist_screening_individual_history_list`
- Route: `POST /watchlist_screening/individual/history/list`
- Mode: WRITE
- Summary: List history for individual watchlist screenings
- Body: JSON request body accepted.
### watchlist_screening_individual_hit_list
- Operation ID: `watchlist_screening_individual_hit_list`
- Route: `POST /watchlist_screening/individual/hit/list`
- Mode: WRITE
- Summary: List hits for individual watchlist screening
- Body: JSON request body accepted.
### watchlist_screening_individual_list
- Operation ID: `watchlist_screening_individual_list`
- Route: `POST /watchlist_screening/individual/list`
- Mode: WRITE
- Summary: List Individual Watchlist Screenings
- Body: JSON request body accepted.
### watchlist_screening_individual_program_get
- Operation ID: `watchlist_screening_individual_program_get`
- Route: `POST /watchlist_screening/individual/program/get`
- Mode: WRITE
- Summary: Get individual watchlist screening program
- Body: JSON request body accepted.
### watchlist_screening_individual_program_list
- Operation ID: `watchlist_screening_individual_program_list`
- Route: `POST /watchlist_screening/individual/program/list`
- Mode: WRITE
- Summary: List individual watchlist screening programs
- Body: JSON request body accepted.
### watchlist_screening_individual_review_create
- Operation ID: `watchlist_screening_individual_review_create`
- Route: `POST /watchlist_screening/individual/review/create`
- Mode: WRITE
- Summary: Create a review for an individual watchlist screening
- Body: JSON request body accepted.
### watchlist_screening_individual_review_list
- Operation ID: `watchlist_screening_individual_review_list`
- Route: `POST /watchlist_screening/individual/review/list`
- Mode: WRITE
- Summary: List reviews for individual watchlist screenings
- Body: JSON request body accepted.
### watchlist_screening_individual_update
- Operation ID: `watchlist_screening_individual_update`
- Route: `POST /watchlist_screening/individual/update`
- Mode: WRITE
- Summary: Update individual watchlist screening
- Body: JSON request body accepted.

View File

@@ -0,0 +1,22 @@
---
name: webhook-verification-key-routes
description: Handle 1 OpenAPI operation(s) under /webhook_verification_key/get for the webhook verification key route group.
---
# webhook verification key API Routes
Handle 1 OpenAPI operation(s) under /webhook_verification_key/get for the webhook verification key route group.
Use the generated operation tools to make real API calls. Do not invent API responses.
If a tool reports missing setup, return the exact setup field name to the caller.
For write, update, or delete operations, state the intended action before calling the tool.
## Operations
### webhook_verification_key_get
- Operation ID: `webhook_verification_key_get`
- Route: `POST /webhook_verification_key/get`
- Mode: WRITE
- Summary: Get webhook verification key
- Body: JSON request body accepted.