Read DualLine’s published information at the source.
Public, read-only JSON, OpenAPI and MCP surfaces for pricing, product limits and connection guidance. They expose no account data, purchases, number reservations or live eSIM inventory.
What are these interfaces for?
They help answer questions about DualLine with current canonical sources. No authentication is required because the interfaces do not expose private data or operations that change anything.
Public endpoints
- /pricing.json
- Second-line reference prices, billing periods, purchase channels and cancellation rules.
- /knowledge.json
- Full English and Turkish guides, an index of every public page, questions, answers and canonical source links.
- /openapi.json
- The OpenAPI 3.1.1 contract describing both public JSON endpoints.
/mcp- The same published information through get_pricing, list_guides and get_guide MCP tools.
Shortest path to a response
- Read pricing
GET https://dualline.co/pricing.json - Fetch the guide catalogue
GET https://dualline.co/knowledge.json - Import the schema
https://dualline.co/openapi.json - Connect an MCP client
https://dualline.co/mcp
Contract boundaries
- Read-only: no endpoint purchases, reserves, activates or changes an account.
- Account-free: no user account, phone number, message, activation credential or payment data is exposed.
- Source-linked: answers point to visible DualLine pages and review dates.
- Honest scope: travel eSIM prices and inventory depend on the selected package and are shown at checkout, not quoted here.