Not unlimited querying
Agents still consume text tokens, app compute, storage, and API calls. The Ayneye value is reducing repeated video-understanding work by reusing durable artifacts.
AI agents
Build video agents on durable World-State, not repeated frame context.
Ayneye gives agent products a reusable video-memory layer: scene state, timelines, evidence bundles, detector confidence, and cost reports. Agents query compact artifacts, cite evidence, expose uncertainty, and stay read-only for high-risk workflows.
REST + MCP Public BetaRead-only agent toolsEvidence-required answersNo destructive actions
Agent operating model
An Ayneye video-agent integration separates video understanding from agent action. First, a bounded CPU-first pass materializes World-State artifacts. Then an agent retrieves those artifacts as structured memory. The agent can answer supported questions, cite evidence references, return insufficient-evidence states, and route high-risk outcomes to human review.
Agents
Agent cost calculator
Plan repeated-query economics across video hours, artifact reuse, and agent loops.
Open →AgentsAgent economics
Understand when durable artifacts reduce repeated visual-context cost and when GPU escalation is still appropriate.
Open →AgentsAgent quickstart
Run the first evaluation path: signup, demo workspace, artifacts, evidence, and read-only agent tools.
Open →FrameworkLangChain guide
Expose scene state, evidence, cost, and Ask Video as separate auditable LangChain tools.
Open →FrameworkCrewAI guide
Split planner, reviewer, and reporter roles while preserving evidence and human gates.
Open →MCPMCP video tools
Live MCP tools for video ingestion, upload, status, artifacts, and evidence-grounded Ask.
Open →Tool surface and boundaries
| Tool | Public Beta behavior | Boundary |
|---|---|---|
| ayneye.create_video | Create and process a URL or HLS video source. | capture_seconds is bounded to the Public Beta session limit |
| ayneye.upload_video | Use a file reference or browser-mediated local-file upload handoff. | An external MCP server cannot read arbitrary local paths |
| ayneye.get_video_status | Read processing and evidence readiness for this run. | Tenant-scoped current run only |
| ayneye.get_video_artifacts | Inspect derived artifacts and evidence readiness. | No unsupported identity or intent claims |
| ayneye.ask_video | Ask a question grounded in evidence materialized for this run. | No guessing when evidence is missing |
What this is not
Not feature-equivalent to every GPU video model
High-motion scenes, subtle expression, dense crowds, and broad cinematic semantics may need specialized GPU models or human review.
Evaluation checklist for agent builders
- Process one representative video or stream window.
- Inspect scene_graph.json, timeline.json, evidence_bundle.json, detector_report.json, and cost.json.
- Ask the same question three ways and compare evidence citations.
- Verify that unsupported questions return insufficient-evidence or review-required states.
- Log every agent tool call with artifact version and evidence reference.
- Confirm high-risk workflows remain human-reviewed.