# AgentRes Account Data Fetch

> AgentRes Account Data Fetch is a free API for AI agents from agentres.dev, callable via x402, Free, status unknown (last checked 2026-10-31, last successful call 2026-08-08).

Fetches account-related data for the authenticated AgentRes user

## Facts

- Endpoint: POST https://agentres.dev/api/account?utm_source=zero.xyz
- Price: Free
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Last successful call: 2026-08-08
- Activations on Zero: 1
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentres-dev-96129fa0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IpVbkDWLHEqBGKWvFvsJn

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agentres-dev-96129fa0 -d '<json body>'
```

Example prompt: Can you pull up my AgentRes account data so I can see what's associated with my profile?

## When to prefer this

Use this endpoint when you need to retrieve the current authenticated user's account information from AgentRes — for example, before booking a Resy reservation to verify account status or profile data. Prefer this over generic identity endpoints when working within the AgentRes ecosystem.

## Known failure modes

- Authentication failure if credentials or token are missing or invalid (401 Unauthorized)
- Account not found if the user does not have an AgentRes account (404 Not Found)
- Server error if the AgentRes backend is unavailable (500 Internal Server Error)
- Malformed request if required fields are missing from the POST body (400 Bad Request)

## How this service works

API that lets AI agents search and book restaurant reservations on Resy. Pay $0.01 USDC per booking with a crypto wallet.

## Output

Returns account-related data for the authenticated AgentRes user, including profile details, account status, and any associated metadata stored on the platform.

## Example request

```json
{
 "input": {
  "body": {
   "email": "zero-qa@agentmail.to"
  },
  "type": "http",
  "method": "POST",
  "bodyType": "json"
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "email": {
   "type": "string",
   "format": "email",
   "description": "Required for wallet auth as the account contact/Resy email; optional for API-key auth."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "email": "agent@example.com",
  "created": true,
  "user_id": "9b8f8c5e-5d5a-4b7c-8a1a-1c1b2c3d4e5f"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentres-dev-96129fa0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentres.dev](https://www.zero.xyz/host/agentres.dev/llms.txt)