> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/profile.md).

# Stripe Link Profile

These read-only blocks retrieve the connected Link account's saved contact and shipping information. They can supply checkout fields, but they do not create or approve a spend request.

## Stripe Link Get Shipping Address

### What it is

Get the delivery addresses saved on the user's Link wallet, with the default one resolved for you. Use it for any purchase that ships something.

### How it works

The block makes an authenticated `GET /shipping_addresses` request to Link and returns the complete list under `addresses`. For `default_address`, it selects the address marked as default, falls back to the first saved address, and returns an empty object when the account has no addresses. If the authenticated Link request fails, the block emits `error` instead of address outputs.

### Outputs

| Output           | Description                                                                                              | Type                   |
| ---------------- | -------------------------------------------------------------------------------------------------------- | ---------------------- |
| error            | Error message if the request failed                                                                      | str                    |
| addresses        | Every shipping address on the account, each with an `id`, `is_default` and an `address` object           | List\[Dict\[str, Any]] |
| default\_address | The address object marked default, or the first one if none is. Empty when the account has no addresses. | Dict\[str, Any]        |

### Possible use case

**Default Delivery**: Prefill a physical purchase with the wallet's `default_address`.

**Address Choice**: Present `addresses` when the user should choose among several saved destinations.

**Fulfillment Validation**: Confirm that the selected address meets the merchant's country and postal-code requirements.

***

## Stripe Link Get User Info

### What it is

Get the Link account holder's name, email and phone. Use it to fill in a checkout that asks who the buyer is. Pairs with Get Shipping Address for anything physical.

### How it works

The block makes an authenticated `GET /userinfo` request to Link and maps the returned name, first name, last name, email, and phone fields directly to block outputs. Missing keys and explicit null values become empty strings so they satisfy the output schema. A failed Link request is reported through `error`.

### Outputs

| Output      | Description                                     | Type |
| ----------- | ----------------------------------------------- | ---- |
| error       | Error message if the request failed             | str  |
| name        | Full name on the Link account                   | str  |
| first\_name | Given name                                      | str  |
| last\_name  | Family name                                     | str  |
| email       | Email on the Link account                       | str  |
| phone       | Phone number in E.164 format, e.g. +15551234567 | str  |

### Possible use case

**Checkout Prefill**: Fill buyer-name and contact fields from the connected Link profile.

**Physical Orders**: Combine contact details with Get Shipping Address for a delivered purchase.

**Missing Data Recovery**: Ask the user for any required value returned as an empty string.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://agpt.co/docs/integrations/block-integrations/profile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.