# NectarPay Hive Account Creator

> NectarPay Hive Account Creator is a paid API for AI agents from nectarpay.crypto-dreamr.com, paid per call via x402, $1/call, status unknown (last checked 2026-09-15).

Creates a new Hive blockchain account for agents or developers via a one-time x402 USDC payment, returning the transaction ID and new username.

## Facts

- Endpoint: POST https://nectarpay.crypto-dreamr.com/api/accounts/create
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nectarpay-hive-account-creator-5c71d493
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uIHTO59gjnjabvrAyQyFg

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 nectarpay-hive-account-creator-5c71d493 -d '<json body>'
```

Example prompt: Create a new Hive blockchain account called 'myagent.hive' for me using NectarPay — I'm ready to pay $1 USDC via x402 and have my sponsor claim ticket ready.

## When to prefer this

Use this endpoint when you need to programmatically create a new Hive blockchain account and are willing to pay $1 USDC per account via the x402 payment protocol. It is the right choice for AI agents or developers bootstrapping Hive identities without manual setup, especially when a sponsor claim ticket is already available.

## Known failure modes

- Invalid or already-used sponsor claim ticket returns an error
- Hive username already taken or invalid format causes rejection
- x402 USDC payment fails or is insufficient
- Network or blockchain congestion causes transaction failure
- Duplicate account creation attempt for same username returns failure

## How this service works

NectarPay creates Hive blockchain accounts for agents and developers from sponsor claim tickets after a one-time x402 USDC payment.

## Output

A JSON object with the Hive transaction ID (tx_id), the newly created username, a success boolean, and a human-readable confirmation message such as "Account 'example.account' successfully created!"

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "memo_key": {
   "type": "string",
   "title": "Memo Key"
  },
  "username": {
   "type": "string",
   "title": "Username"
  },
  "owner_key": {
   "type": "string",
   "title": "Owner Key"
  },
  "active_key": {
   "type": "string",
   "title": "Active Key"
  },
  "posting_key": {
   "type": "string",
   "title": "Posting Key"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tx_id": "hive_transaction_id",
  "message": "Account 'example.account' successfully created!",
  "success": true,
  "username": "example.account"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nectarpay-hive-account-creator-5c71d493/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from nectarpay.crypto-dreamr.com](https://www.zero.xyz/host/nectarpay.crypto-dreamr.com/llms.txt)
