> ## Documentation Index
> Fetch the complete documentation index at: https://docs.crossmint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete Buyer Profile

> Deletes a buyer profile owned by the authenticated user. Checkouts that already ran with it keep their captured buyer-profile provenance.

**API scope required**: `agent-checkouts.buyer-profiles.delete`



## OpenAPI

````yaml delete /unstable/agent-checkouts/buyer-profiles/{id}
openapi: 3.0.3
info:
  title: Crossmint Agent Checkouts API
  version: unstable
  description: >-
    Drive a real, automated browser session through any merchant's checkout on
    behalf of a signed-in user.


    You hand the API a product URL, an optional natural-language instruction,
    and a hard maximum cost. Crossmint runs a browser through the merchant's
    checkout pages, pausing for *user actions* (shipping, payment, anything only
    a human can answer) which you respond to with values that satisfy a supplied
    JSON Schema. There are no webhooks in v1 — poll the checkout until it
    reaches a terminal state.


    ## Base URL


    `https://www.crossmint.com/api` (production) ·
    `https://staging.crossmint.com/api` (staging)


    ## Authentication


    Every request requires **two** credentials:


    - `X-API-KEY` — a client-side API key (`ck_...`) with the
    `agent-checkouts.*` scopes.

    - `Authorization: Bearer <jwt>` — a JWT identifying the end user, issued by
    an external auth provider your project trusts. Without it the API returns
    `401`.


    <Note>This API lives under the `unstable` namespace. The schema may change —
    pin and re-test on upgrades.</Note>
servers:
  - url: https://www.crossmint.com/api
    description: Production
  - url: https://staging.crossmint.com/api
    description: Staging
security:
  - ApiKeyAuth: []
    BearerAuth: []
tags:
  - name: Agent Checkouts
    description: Create, poll, respond to, and cancel browser-driven checkouts.
  - name: Buyer Profiles
    description: >-
      Subject-scoped buyer identity and shipping address the agent can prefill
      during a checkout run. Payment data is never stored.
paths:
  /unstable/agent-checkouts/buyer-profiles/{id}:
    delete:
      tags:
        - Buyer Profiles
      summary: Delete Buyer Profile
      description: >-
        Deletes a buyer profile owned by the authenticated user. Checkouts that
        already ran with it keep their captured buyer-profile provenance.


        **API scope required**: `agent-checkouts.buyer-profiles.delete`
      operationId: deleteBuyerProfile
      parameters:
        - $ref: '#/components/parameters/BuyerProfileId'
      responses:
        '204':
          description: The buyer profile was deleted.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
components:
  parameters:
    BuyerProfileId:
      name: id
      in: path
      required: true
      description: The buyer profile id (returned by create).
      schema:
        type: string
        format: uuid
  responses:
    Unauthorized:
      description: >-
        Missing or invalid authentication. A valid `X-API-KEY` and
        `Authorization: Bearer <jwt>` are both required.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    Forbidden:
      description: >-
        The API key lacks the required scope, or Agent Checkouts is not enabled
        for this project.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    NotFound:
      description: No checkout, action, or buyer profile with the given id.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  schemas:
    Error:
      type: object
      properties:
        statusCode:
          type: integer
        error:
          type: string
        message:
          type: string
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-KEY
      description: Client-side API key (`ck_...`) with the `agent-checkouts.*` scopes.
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        JWT identifying the end user, issued by an external auth provider your
        project trusts.

````