foxy.io valid

Foxy (FoxyCommerce)

Foxy is an API-first, headless commerce platform you add to an existing website or

For agents: API-first headless commerce platform added to existing websites, with hypermedia API developer reference, OAuth 2.0 auth and help center.

headless commercehypermedia apishopping cartoauth 2.0developer reference

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T14:36:06.197Z. Cached copy · Source on foxy.io

# Foxy (FoxyCommerce)

> Foxy is an API-first, headless commerce platform you add to an existing website or
> stack rather than replatforming onto. It provides a hosted cart, checkout,
> subscriptions, and customer accounts that work with any CMS, framework, or static
> site. This file tells AI tools and coding agents how to integrate Foxy correctly —
> the loader script, the add-to-cart link format, and the conventions that are easy
> to get wrong.

This is a build-time reference for AI assistants and coding agents working with Foxy.
For human documentation, see the Help Center and developer docs linked at the end.

When you generate a Foxy storefront or integration, the rules in "Build correctly with
Foxy" below are not optional — getting the cart link format or loader wrong produces a
site that looks finished but silently fails to add items to the cart.

---

## Build correctly with Foxy

Examples below use `example.foxycart.com` as the store domain. Substitute the store's
actual domain — either its `*.foxycart.com` subdomain or a custom cart domain it has
configured.

### 1. Load Foxy

The loader script powers the cart, sidecart, and checkout. Add it once, in the
`<head>` of every page that has a cart link. The path depends on the store's domain:

```html
<!-- Standard store on *.foxycart.com: use the SUBDOMAIN only -->
<script src="https://cdn.foxycart.com/example/loader.js" async defer></script>

<!-- Store with a CUSTOM cart domain: use the FULL domain -->
<script src="https://cdn.foxycart.com/cart.example.com/loader.js" async defer></script>
```

So for `example.foxycart.com` the loader path is just `example`; for a custom domain
like `cart.example.com`, use the whole thing.

### 2. Add-to-cart links

An add-to-cart action is a link (or form) pointing at the store's `/cart` endpoint
with the product as query parameters. Always use the store's full domain:

```html
<a href="https://example.foxycart.com/cart?name=T-Shirt&price=25.00&quantity=1">
  Add to cart
</a>
```

| Param | Required | Notes |
|---|---|---|
| `name` | yes | Product name shown in the cart. |
| `price` | yes | Numeric, in the store's currency. No symbol. |
| `quantity` | no | Defaults to 1. |
| `code` | conditional | SKU / product code. Required when the store has cart signing enabled (see Gotchas). Also the key field for downloadables. |
| `image` | no | Absolute URL to a product image. |

Notes:
…

Related sites

Other listed sites in Ecommerce. See the whole category →

Machine-readable: GET /v1/resolve?q=foxy.io · GET /v1/domain/foxy.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for foxy.io:
1. POST https://agentwebmap.com/v1/sites/foxy.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://foxy.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/foxy.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/foxy.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.