Jatevo Policy

Endpoint Types Policy

This policy explains how Jatevo classifies seller partner endpoints and route types so customers can compare options with clearer source, region, latency, and verification context.

Last updated: June 3, 2026

Overview

Jatevo may list or route requests through endpoints operated by Jatevo, verified direct API routes, or seller partners. These endpoint labels are designed to make the marketplace more transparent before customers choose a route.

The label is a disclosure and comparison aid. It is not a guarantee of uptime, latency, model behavior, price, provider affiliation, or future availability.

Endpoint labels

Verified Direct API

A route we have verified as a direct API endpoint for the listed seller, provider, or service.

  • Best suited when customers want the clearest source classification.
  • May be prioritized when performance, availability, and pricing are otherwise comparable.

Partner-Managed Endpoint

A route operated, supplied, or managed by a seller partner instead of directly by Jatevo.

  • Performance, availability, behavior, supported models, and limits may vary by partner.
  • Jatevo may monitor health, latency, and request outcomes to help customers compare options.

Experimental Endpoint

A route that is available for evaluation but has not completed full verification.

  • Best used for testing, fallback, or price/performance exploration.
  • Customers should treat this label as a caution that the source, behavior, or reliability may change.

Comparison signals

Jatevo may show operational signals beside each endpoint label to help customers understand routing tradeoffs before use.

Region
Approximate serving market or routing area, such as SEA, Asia, US, or EU.
Latency
Recent observed response speed from Jatevo checks or customer traffic patterns.
Verification
Whether Jatevo has checked the endpoint type and how confident the current classification is.
Availability
Observed route health, recent failures, and whether the endpoint is suitable for production traffic.

Customer choice

Customers may choose endpoints based on verification status, region, latency, availability, price, and model support. When direct API routes and partner-managed routes are both available, Jatevo should present the distinction clearly.

If a route is not fully verified, Jatevo may classify it as experimental or separate it from the main verified market until additional checks are complete.

Seller partner responsibilities

Seller partners are responsible for providing accurate information about the endpoints they offer, including source type, supported models, market region, availability limits, and material operational constraints.

Jatevo may update, downgrade, hide, or relabel an endpoint if monitoring, customer reports, or partner information indicates that the current label is inaccurate or incomplete.

Relationship to privacy

This page explains endpoint classification and marketplace transparency. The Privacy Policy explains how Jatevo handles user information, API request data, operational metadata, and service provider processing.

Endpoint labels should be shown near the relevant seller, route, or selection screen so customers do not need to read the privacy policy to understand what kind of endpoint they are choosing.

Changes

Jatevo may update this policy as endpoint categories, seller partner requirements, or marketplace disclosures evolve. Material updates will be reflected by the last updated date on this page.