# BRAINIAC Token Vesting Schedule Audit

> BRAINIAC Token Vesting Schedule Audit is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.05/call, status unknown (last checked 2026-11-13).

Audits a token vesting schedule by validating allocations, unlock timelines, cliff logic, distributions, and supply totals, returning warnings and a full unlock schedule.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/tokenomics/token-vesting-schedule-audit?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-token-vesting-schedule-audit-38bf3921
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VKsANJbdgUFoijEozybLj

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 brainiac-token-vesting-schedule-audit-38bf3921 -d '<json body>'
```

Example prompt: Audit my token vesting schedule: total supply is 1,000,000 tokens. I have two allocations — 'team' for address 0xAAA with 500,000 tokens using a linear model starting 2025-01-01T00:00:00Z, a 12-month cliff (cliffMode: before_vesting), 24-month vesting, monthly unlock frequency, and no initial unlock; and 'investors' for 0xBBB with 200,000 tokens using a linear model starting 2025-01-01T00:00:00Z, 6-month cliff (cliffMode: included), 18-month vesting, monthly unlocks, and 10% initial unlock. Tell me if there are any warnings, overlapping schedules, or supply mismatches.

## When to prefer this

Use this endpoint when you need to programmatically audit or validate a token vesting schedule before or after deployment — especially when checking for supply inconsistencies, duplicate beneficiaries, overlapping timelines, cliff logic errors, or when you need a full computed unlock schedule with cumulative issuance across multiple allocations. It is purpose-built for tokenomics compliance and is more thorough than manual spreadsheet checks. It is not a live on-chain reader — it audits the data you submit, not wallet balances or historical transfers.

## Known failure modes

- Missing required allocation fields (id, beneficiary, amount, model) causes the allocation to be omitted from the schedule but still counted in supply totals
- Amounts that don't sum to the declared supply trigger a supply mismatch warning
- Overlapping or duplicate beneficiary schedules produce specific warning codes
- Timestamps not in ISO 8601 UTC format (ending in Z) are rejected by schema validation
- More than 40 allocations or 100 distributions exceeds schema limits and will cause a validation error
- Custom allocations with no unlock list or linear allocations with conflicting custom unlocks may produce incomplete schedules
- Integer division rounding on initial unlock percent may leave remainder in vesting amount, noted in limitations

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with: audit_status ('pass', 'warnings', or 'fail'), an array of warnings (each with a code and detail), a computed unlock_schedule listing every unlock event with timestamp, amount, beneficiary, allocation ID, and cumulative amounts, total_allocated sum across all allocations, and a limitations array explaining computation assumptions and rounding behavior.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "supply": {
   "type": "string"
  },
  "allocations": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "id",
     "beneficiary",
     "amount",
     "model"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "model": {
      "enum": [
       "linear",
       "custom"
      ],
      "type": "string"
     },
     "start": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{3})?Z$"
     },
     "amount": {
      "type": "string"
     },
     "unlocks": {
      "type": "array",
      "items": {
       "type": "object",
       "required": [
        "at",
        "amount"
       ],
       "properties": {
        "at": {
         "type": "string",
         "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{3})?Z$"
        },
        "amount": {
         "type": "string"
        }
       },
       "additionalProperties": false
      },
      "maxItems": 64
     },
     "cliffDate": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{3})?Z$"
     },
     "cliffMode": {
      "enum": [
       "included",
       "before_vesting"
      ],
      "type": "string"
     },
     "beneficiary": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "initialUnlockAmount": {
      "type": "string"
     },
     "cliffDurationSeconds": {
      "type": "integer",
      "maximum": 3153600000,
      "minimum": 0
     },
     "initialUnlockPercent": {
      "type": "string",
      "pattern": "^(100(?:\\.0{1,4})?|(?:0|[1-9]\\d?)(?:\\.\\d{1,4})?)$"
     },
     "unlockFrequencySeconds": {
      "type": "integer",
      "maximum": 3153600000,
      "minimum": 1
     },
     "vestingDurationSeconds": {
      "type": "integer",
      "maximum": 3153600000,
      "minimum": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 40,
   "minItems": 1
  },
  "distributions": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "allocationId",
     "amount",
     "at"
    ],
    "properties": {
     "at": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}(?:\\.\\d{3})?Z$"
     },
     "amount": {
      "type": "string"
     },
     "beneficiary": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1
     },
     "allocationId": {
 
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "warnings": [
   {
    "code": "duplicate_beneficiary",
    "detail": "Beneficiary 0x1111111111111111111111111111111111111111 has allocations team, team-bonus."
   },
   {
    "code": "overlapping_schedule",
    "detail": "Allocations team and team-bonus cover overlapping times."
   }
  ],
  "limitations": [
   "Only the supply, allocations, and distribution records in this request were audited. No wallet balance or token transfer was read.",
   "Timestamps are UTC instants and must end in Z. No timezone is applied.",
   "Amounts are integers in the caller's smallest unit. An initial unlock percent uses integer division, and any remainder stays in the vesting amount.",
   "allocation_percentage is truncated to 4 decimal places.",
   "A linear schedule releases the initial unlock at the start. cliffMode before_vesting places later unlocks one frequency apart after the cliff. cliffMode included starts the clock at the start and withholds vesting unlocks that fall before the cliff until the cliff.",
   "When the vesting duration is not a multiple of the unlock frequency, the last unlock is at the vesting end and receives the remaining tokens. Earlier unlocks are equal integer shares.",
   "The last unlock includes any remainder from integer division, so a complete schedule adds up to the allocation amount.",
   "A custom allocation uses only its unlock list. Linear fields on a custom allocation are not used, and a custom unlock list on a linear allocation is not used.",
   "A distribution is compared only when its allocationId matches an allocation in this request.",
   "Allocations with missing parameters are counted in the supply totals and omitted from the unlock schedule."
  ],
  "audit_status": "warnings",
  "total_allocated": "700000",
  "unlock_schedule": [
   {
    "at": "2026-02-01T00:00:00.000Z",
    "kind": "unlock",
    "amount": "50000",
    "beneficiary": "0x1111111111111111111111111111111111111111",
    "allocation_id": "team-bonus",
    "cumulative_amount": "50000",
    "cumulative_issuance": "50000"
   },
   {
    "at": "2026-03-01T00:00:00.000Z",
    "kind": "unlock",
    "amount": "50000",
    "beneficiary": "0x1111111111111111111111111111111111111111",
    "allocation_id": "team-bonus",
    "cumulative_amount": "100000",
    "cumulative_issuance": "100000"
   },
   {
    "at": "2026-03-02T00:00:00.000Z",
    "kind": "unlock",
    "amount": "200000",
    "beneficiary": "0x1111111111111111111111111111111111
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-token-vesting-schedule-audit-38bf3921/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
