hawker. For agents

Hawker plugin marketplace / review first

Connect capability.
Keep control.

Hawker lets merchants extend an agent with reviewed commerce capabilities — without turning a public card into a credential, an approval or a blank cheque.

Browsing this catalogue is discovery only. This page cannot install a plugin, accept terms, connect a provider or grant a capability.

Open publisher review status

Reviewed catalogue

Plugins with
visible limits.

Every public release has a declared capability, an isolated AI-test receipt and independent review behind it. Reviewed does not mean connected; connected never means unlimited access.

Read the review path

Loading plugin catalogue

Loading marketplace catalogue

Commercial boundary: a publisher can propose paid access, but Hawker’s percentage, merchant approval, refund route and entitlement revocation must be settled before a sale exists. A card never creates a charge, connection or entitlement.

Connection, explained

A private route,
controlled by people.

A plugin can make an agent more useful, but the accountable merchant remains responsible for the account it touches, the data it can see and the actions it may propose.

For merchants

You approve the boundary.

  1. Choose a reviewed release.Catalogue visibility is not a connection, an entitlement or a provider certification.
  2. Review the exact request.An agent may suggest a narrow capability; it cannot approve its own permissions.
  3. Connect privately.Hawker keeps provider authorisation server-side, not in a browser page, card or prompt.
  4. Stop it at any time.Consent, scopes and future use can be revoked without rewriting past evidence.

Reviewed does not mean connected. Connected does not mean an agent has unlimited access.

Connector queue

What is being designed
next.

These provider-specific connectors are visible early so merchants and builders can understand the intended boundary. They are proposals, not installable plugins or live integrations.

Commerce platform

Not connected

Shopify

Merchant-authorised catalogue, order and fulfilment operations through official supported routes — with every write kept behind a Hawker mandate and final recheck.

Read the connector plan

Commerce platform

Not connected

WooCommerce

Merchant-owned store sync with hardened self-hosted endpoint controls, verified webhooks and no direct agent access to WordPress or provider credentials.

Read the connector plan

What makes a plugin usable

Scope, evidence,
then access.

  1. 01

    Declare the capability

    A versioned manifest says exactly what a plugin requests — no hidden extension of authority.

  2. 02

    Pass the boundary

    Review, conformance checks and merchant consent happen before a plugin can touch a consequential workflow.

  3. 03

    Keep a receipt

    Install, update, payment entitlement and revoke decisions need a traceable record and a safe stop path.