Knit Pay abilities, governed through the Bridge

An agent can create a Knit Pay payment request that returns a payment link to share, and look up a payment by its ID to read its current status and details.

Abilities
22 destructive
Active installs
2K+
Rating
98% (100 ratings)
Version checked
9.6.4.0
Requires
WP 6.2+, PHP 8.1+
Last updated
2026-11-07
Abilities verified
10 November 2026
Installs and rating as of
10 November 2026

What has to be true first

The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.2), plus PHP 8.1 or later and the plugin active. The permission check for all 2 abilities runs through a helper or filter, so no single capability is listed here.

A note on the count below

Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.

The 2 Knit Pay abilities

Grouped by what each one can change. Every one starts off until you enable it.

Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.

Destructive 2

  • Destructive

    Create Payment

    Creates a new payment request using Knit Pay. Returns a payment link (pay_redirect_url) that you can share with the customer so they can complete the payment. After the customer pays, use the knit-pay/get-payment ability with the returned payment id to check the payment status.

    Permission
    Custom checkpermission is checked by the plugin's own code, so no single capability could be read from it
    MCP tool
    aafm-bridge-knit-pay-create-payment
  • Destructive

    Get Payment

    Retrieves a Knit Pay payment by its ID and returns its current status and details. Use this after sharing the payment link with a customer to check whether they have completed, failed, or not yet attempted the payment. Common status values: open (not yet paid), success (payment completed), failure (payment failed), cancelled (customer cancelled).

    Permission
    Custom checkpermission is checked by the plugin's own code, so no single capability could be read from it
    MCP tool
    aafm-bridge-knit-pay-get-payment

How to switch these on

Four steps from two active plugins to a governed connection.

  1. Install Knit Pay and Agent Abilities for MCP

    Both plugins need to be active on the same WordPress site. Knit Pay registers its own abilities; this plugin discovers and governs them.

  2. Open the Plugins’ own tools screen

    In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.

  3. Enable one ability at a time

    Every ability from Knit Pay starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.

  4. Connect as a least-privilege user

    Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.

Read more in how bridging works or the full documentation.

Frequently asked questions

Does Knit Pay work with the Bridge?

Yes. Knit Pay calls wp_register_ability() for 2 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.

Do Knit Pay's abilities register automatically?

Yes, once Knit Pay is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.

Does Knit Pay need anything special to work with the Bridge?

The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.2), plus PHP 8.1 or later and the plugin active. The permission check for all 2 abilities runs through a helper or filter, so no single capability is listed here.

More Ecommerce plugins

An agent can list, create, update, and delete WooCommerce products, and list orders, add order notes, or change an order's status, all through the same REST layer as the wc/v3 API.

Ecommerce7M+ active installsVerified 28 September 2026
2 read2 write3 destructive
Built-in integration tooView abilities

An agent can pull the connected Stripe account's status and balance, and read charges, payment intents, disputes, payouts and balance transactions by ID or as lists, all read-only, once WooCommerce and the plugin's ability feature flag are both enabled.

Ecommerce700K+ active installsVerified 28 September 2026
10 read
View abilities

An agent can check whether the store's PayPal account is connected, list configured payment methods, and look up a PayPal order's captures, refunds and shipment tracking, all read-only, once WooCommerce and the plugin's ability feature flag are both enabled.

Ecommerce700K+ active installsVerified 28 September 2026
4 read
View abilities

Verified from Knit Pay's own free wordpress.org code (version 9.6.4.0) on 10 November 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, KnitPay or Knit Pay. Back to the full directory.

Back to the plugin directory

Bridge Knit Pay, keep the same control.

Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.

Off by default. Capability checked on every call.