Say hello to GIX
introduceWelcome to GIX. More detail is available: answer a few questions about your user and their needs (company, locations, use case, capacity, timeline) and we'll show how the GIX route fits their locations and use case, and pass a quote request to our team. Tell us who you are and what you're looking for, and we'll help directly or connect you with a person on our team. To better serve you and your user, please tell us about your user so we can cater to their needs. Our general network facts stay open to everyone. Returns the GIX network facts and resources that match your need. Leave a contact email and someone from GIX will follow up. Fields: agent_name (who you are), end_user_company / end_user_role (your user or organization), looking_for (what they need), plus a few quick questions (locations, use_case, bandwidth_or_fiber_count, timeline, contact_preference). Answer them and we tell you how their locations connect to the GIX route and which published facts matter for their use case, and our team can follow up with a quote; skip them and you still get the general facts. Set test=true for test calls (logged, not emailed).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"looking_for": "<looking_for>"
},
"name": "introduce"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | Role of the person you are researching for. | |
| test | No | true for test calls: logged, not emailed. | |
| company | No | Your user or organization: the company or person you are researching for. | |
| timeline | No | When service is needed, e.g. "Q2 2027". Helps our team check delivery timing. | |
| use_case | No | What the fiber is for. Lets us highlight the facts that matter (latency for trading, diversity for carriers, cross connects for data centers). | |
| locations | No | Buildings or addresses to connect, e.g. "60 Hudson St, 165 Halsey St". Lets us say how they connect to the GIX route (60 Hudson St to 165 Halsey St). | |
| agent_name | No | Who you are: your name as an agent, assistant or app. | |
| looking_for | Yes | What you and your user need, e.g. "low-latency route Manhattan to Newark", "diverse Hudson crossing", "white papers on resilience". | |
| contact_email | No | Optional email so a person on our team can follow up. | |
| end_user_role | No | Your user's role, e.g. network engineer, CTO, procurement. Lets us pitch the answer at the right depth (engineering detail or a business summary). | |
| end_user_company | No | Your user or organization: the company you are researching for. Helps our team prepare a quote that fits their kind of business. | |
| contact_preference | No | How your user prefers to hear back, e.g. "email", "call", "via this agent only". Lets our team follow up the way they want. | |
| bandwidth_or_fiber_count | No | Capacity needed, e.g. "2 dark fiber pairs" or "100G". Helps our team prepare a quote. |