# Declared Spatial Adjacency Check

> Declared Spatial Adjacency Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035008/call, status unknown (last checked 2026-10-15).

Validates room adjacency requirements against a supplied topology graph, reporting unknown and contradictory declarations without issuing architectural approval.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/architecture/adjacency?utm_source=zero.xyz
- Price: $0.035008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/declared-spatial-adjacency-check-77c119e0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WHlpLdOQJWASbUjsFpfiy

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 declared-spatial-adjacency-check-77c119e0 -d '<json body>'
```

Example prompt: Check my room adjacency requirements against the building topology I've provided — flag any unknown rooms and any contradictions between what I declared and what the topology shows. The data is synthetic.

## When to prefer this

Choose this endpoint when you need to programmatically validate declared spatial adjacency constraints against an explicit topology graph — particularly when catching unknown room references and logical contradictions before committing to an architectural design. It is purpose-built for topology-driven consistency checking rather than geometric or visual floor-plan analysis.

## Known failure modes

- Missing required 'rooms' or 'requirements' arrays returns a validation error
- Room count exceeding 32 or requirement count exceeding 64 returns a schema error
- Topology references rooms not present in the rooms array may trigger unknown-room flags
- Invalid or unrecognized dataClass enum value returns a bad request error
- Empty requirements array (below minItems:1) is rejected
- Malformed topology edges may cause incomplete contradiction detection

## How this service works

Compare bounded room requirements with supplied topology; report unknown and contradictory declarations, not architectural approval. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

A structured report listing any unknown rooms referenced in the requirements but absent from the topology, and any contradictory adjacency declarations where the requirements conflict with the supplied topology. The endpoint does not approve the architecture — it only surfaces inconsistencies.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rooms": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "topology": {
   "type": "array",
   "maxItems": 64,
   "minItems": 0
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requirements": {
   "type": "array",
   "maxItems": 64,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/declared-spatial-adjacency-check-77c119e0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)