How Apexverse fits into an AI stack
- Run a lightweight public JSON test if you want to validate extraction quality.
- Sign up with Google or email and choose a monthly or annual plan.
- Configure crawl scope, output behavior, and delivery settings in the workspace.
- Connect supported vector databases from the dashboard when needed.
- Recrawl and refresh content as the source site changes.
POST /v1/jobs
{
"source_url": "https://docs.example.com",
"mode": "json_export",
"crawl_policy": "docs-site"
}
Public JSON Test
The public website flow is intended for lightweight evaluation only. It should accept a single URL, return JSON output only, and be protected by backend rate limits.
- Single public URL input
- JSON-only response path
- No production credentials
- No vector connector exposure
Account and Billing
Teams can sign up with Google or email, choose a monthly or annual plan, and complete secure card checkout before using paid workspace features.
- Google signup
- Email and password signup
- Monthly billing
- Annual billing
Outputs and Delivery
Apexverse can prepare structured outputs for downstream AI pipelines, human review, or direct delivery into supported retrieval infrastructure.
- JSON exports
- Markdown exports
- Chunked text plus metadata
- CSV metadata and operational views
Vector Delivery
Vector database configuration is handled in the authenticated workspace after signup. Customer-managed connector credentials are not part of the public evaluation flow.
- Pinecone alignment
- Qdrant alignment
- Weaviate alignment
- Dashboard-based connector setup
Operational Controls
Teams can define how content should be recrawled, monitored, and handed off into downstream systems so website changes do not leave AI experiences stale.
- Scheduled recrawls
- Change-aware refresh workflows
- Connector and delivery review
- Operational visibility across jobs