Code and technical data displayed on a screen

DOCUMENTATION

Eyecosystems Data API and MCP

Technical overview of plug-and-play API and MCP delivery for structured accessibility community data. Request current access and integration details.

The examples below illustrate possible request, response, and data-schema patterns. They do not confirm that a specific endpoint, field, rate limit, or integration is currently available. Eyecosystems delivers data through API and MCP options. Request technical documentation for current details.

Getting Started

Eyecosystems delivers structured accessibility community data through plug-and-play API and MCP integrations. Human-in-the-loop review and provenance add context to records. The examples on this page are illustrative; confirm current endpoints, fields, authentication, and access details with our team.

For current access options and technical documentation, request technical documentation.

Base URL https://api.eyecosystems.com/v1

All requests must be made over HTTPS. HTTP requests will be rejected. All responses use UTF-8 encoding.

Authentication

Authenticate by passing your API key in the Authorization header as a Bearer token. All requests require a valid API key.

HTTP Header
Authorization: Bearer YOUR_API_KEY
cURL
curl https://api.eyecosystems.com/v1/records \
  -H "Authorization: Bearer YOUR_API_KEY"

To obtain an API key, contact the Eyecosystems team. Keys are issued per subscriber and should be kept confidential. Do not expose your key in client-side code.

Endpoints

All endpoints return JSON. Paginated list responses include total, limit, offset, and data fields.

GET /records

Illustrative pattern for listing records with city, state, and type filters and paginated results. Confirm current endpoint behavior with the Eyecosystems team.

Parameter Type Description
citystringFilter by city name (e.g. Jacksonville)
statestringFilter by two-letter state code (e.g. FL)
typestringFilter by organization type (e.g. nonprofit_advocacy)
limitintegerNumber of results per page. Default: 25. Max: 100
offsetintegerPagination offset. Default: 0
cURL
curl "https://api.eyecosystems.com/v1/records?city=Jacksonville&state=FL&limit=10" \
  -H "Authorization: Bearer YOUR_API_KEY"
JSON Response
{
  "total": 1,
  "limit": 10,
  "offset": 0,
  "data": [
    {
      "eyeco_id": "jax-0001",
      "name": "Jacksonville Community Resource",
      "type": "nonprofit_community",
      "verified_at": "2026-04-08T14:32:00Z",
      "verifier": "human_reviewer",
      "city": "Jacksonville",
      "state": "FL",
      "contact_verified": true,
      "tags": ["community", "blind-and-low-vision", "community-resource"],
      "verification_method": "human_eye_spy_network",
      "provenance_hash": "sha256:e3b0c44...",
    }
  ]
}
GET /records/:id

Illustrative pattern for retrieving a record by its eyeco_id. Confirm current endpoint behavior and available fields with the Eyecosystems team.

cURL
curl "https://api.eyecosystems.com/v1/records/jax-0042" \
  -H "Authorization: Bearer YOUR_API_KEY"
JSON Response
{
  "eyeco_id": "jax-0042",
  "name": "Florida Council of the Blind: Jacksonville Chapter",
  "type": "nonprofit_advocacy",
  "verified_at": "2026-04-08T14:32:00Z",
  "verifier": "human_reviewer",
  "city": "Jacksonville",
  "state": "FL",
  "contact_verified": true,
  "tags": ["advocacy", "peer-support", "community-resource"],
  "updated_at": "2026-04-08T14:32:00Z",
  "verification_method": "human_eye_spy_network",
  "provenance_hash": "sha256:e3b0c44..."
}
GET /records/search

Full-text search across record names, tags, and descriptions. Returns ranked results matching the query.

Parameter Type Description
qstringSearch query string (required)
citystringOptionally scope results to a city
statestringOptionally scope results to a state
limitintegerResults per page. Default: 25
offsetintegerPagination offset. Default: 0
cURL
curl "https://api.eyecosystems.com/v1/records/search?q=peer+support&state=FL" \
  -H "Authorization: Bearer YOUR_API_KEY"

Data Schema

Record structure depends on current data availability. The fields below are illustrative; request technical documentation for confirmed fields and access details.

Field Type Description
eyeco_id string Unique Eyecosystems record identifier. Format: {city_code}-{sequence}
name string Full verified name of the organization, service, or resource
type string Organization type. Values: nonprofit_advocacy, nonprofit_community, government_service, assistive_tech, education, peer_support, event
verified_at ISO 8601 datetime Timestamp of the most recent human verification
verifier string Verification method identifier. Currently always human_bvi_reviewer
city string City of the organization's primary location
state string Two-letter US state code
contact_verified boolean true if contact information has been verified in this verification cycle
tags array of strings Taxonomy tags for filtering and discovery. Examples: advocacy, peer-support, community-resource
updated_at ISO 8601 datetime Timestamp of the last record update (any field change)
provenance string Describes the source and review history associated with a record
verification_method string The human-in-the-loop review method associated with a record, when available
provenance_hash string Provenance details that describe the source and review history of a record

Rate Limits

Rate limits are enforced per API key. Exceeding the limit returns a 429 Too Many Requests response. The Retry-After header indicates when you may retry.

Core Verification
By request
Current rate limits are provided with technical documentation.
Enterprise & AI Integration
Custom
Discuss integration needs and usage limits with the Eyecosystems team.

Current access limits and response details are provided with technical documentation.

Support

Contact us with questions about data access, available fields, or integration options.

Email: contact@eyecosystems.com

For partnership or Enterprise inquiries, use the contact form and select "Data Access" as the purpose.

Request a trial API key, sample data set, and current technical documentation from the Eyecosystems team.