tools-registry

วิธีใช้งาน Treg People Search API --- title: "วิธีใช้งาน Treg People Search API" description: "ใช้ Treg people search API จาก Claude Code หรือ Codex: การตั้งค่า, พรอมต์สำหรับค้นหา เสริมข้อมูล และตรวจสอบ, การเรียก HTTP แบบดิบ, ค่าใช้จ่ายต่อการเรียก และชุดทดสอบรีเกรสชันด้วย Apidog CLI" canonical_url: apidog.com cover_image: assets.apidog.com --- API ค้นหาบุคคลของ Treg มอบโทเคนหนึ่งตัวให้เอเจนต์เขียนโค้ดของคุณสำหรับค้นหาบุคคล อีเมลที่ทำงานของพวกเขา และคำตัดสินว่าอีเมลเหล่านั้นเป็นของจริงหรือไม่ คุณติดตั้ง CLI treg ลงชื่อเข้าใช้หนึ่งครั้ง แล้ว Claude Code หรือ Codex จะเรียกเครื่องมือที่ถูกจัดเส้นทาง เช่น treg.people.search, treg.people.email.find และ treg.people.email.verify Treg จะเลือกผู้ให้บริการ ฉีดคีย์ของผู้ให้บริการบนเซิร์ฟเวอร์ของตน และเรียกเก็บเงินแต่ละครั้งจากยอดคงเหลือแบบเติมเงินในอัตราของผู้ให้บริการเอง {% cta apidog.com %} ลองใช้ Apidog วันนี้ {% endcta %} คู่มือนี้ครอบคลุมการตั้งค่า พรอมต์สำหรับเอเจนต์สามแบบ (ค้นหา, เสริมข้อมูล, ตรวจสอบ) การเรียก HTTP แบบดิบที่อยู่เบื้องหลัง และชุดการทดสอบถดถอย Apidog CLI ที่เอเจนต์ของคุณรัน Treg people search API คืออะไร? Treg คือแค็ตตาล็อกเครื่องมือแบบโอเพนซอร์สสำหรับเอเจนต์ ซึ่งเอกสารของตัวเองอธิบายว่า "OpenRouter แต่สำหรับเครื่องมือของเอเจนต์แทนที่จะเป็นโมเดล" หนึ่ง base URL (https://treg.to) และหนึ่งโทเคนเข้าถึงเครื่องมือกว่า 4,100 รายการจากผู้ให้บริการ 123 ราย สำหรับการค้นหาบุคคล เครื่องมือที่ถูกจัดเส้นทางจะเลือกผู้ให้บริการต่อการเรียกหนึ่งครั้ง ลองรายถัดไปเมื่อไม่พบ และรายงานค่าใช้จ่ายของการเรียกทุกครั้งในเฮดเดอร์ตอบกลับ !assets.apidog.com ฝั่งการค้นหาบุคคลคือชุดความสามารถที่ถูกจัดเส้นทางขนาดเล็ก นี่คือสิ่งที่แค็ตตาล็อกสาธารณะระบุไว้เมื่อวันที่ 3 พฤศจิกายน 2026: | เครื่องมือที่ถูกจัดเส้นทาง | ทำอะไร | อินพุตที่รับ | ผู้ให้บริการที่อยู่เบื้องหลัง | | --- | --- | --- | --- | | treg.people.search | ค้นหาบุคคลในบริษัทหรือตามคำอธิบาย | q, company_domain, company_domain + title, title, full_name | 26 | | treg.people.email.find | คืนค่าอีเมลที่ทำงานที่ตรงที่สุด | domain + full_name, domain + first_name + last_name, linkedin_url | 30 | | treg.people.email.verify | ตรวจสอบว่ากล่องจดหมายรับอีเมลได้หรือไม่ | email | 17 | | treg.companies.enrich | ข้อมูลบริษัท (firmographics) | โดเมนของบริษัท | 30 | หน้าค้นหาบุคคลอ้างอิงผู้ให้บริการ 16 รายสำหรับการค้นหาบุคคล ตัวเลขข้างต้นมาจากแค็ตตาล็อกสด ดังนั้นคาดว่ามันจะเปลี่ยนแปลงได้ ทำไมต้องใช้ตัวรวบรวมแทนคีย์ Apollo หรือ Hunter? มีสองเหตุผล เอเจนต์ของคุณไม่เคยถือคีย์ของผู้ให้บริการ และคุณจ่ายต่อคำตอบแทนที่จะจ่ายต่อที่นั่ง หน้าเพจของ Treg อ้างอิง People Search Bench ของ LessieAI (119 งาน): ในงานด้าน B2B prospecting ของมัน Claude Code เพียงลำพังตอบถูก 43% และ Claude Code ที่ใช้ Treg ตอบถูก 78.2% นั่นคือกราฟของผู้ขายเอง จึงควรถือเป็นคำกล่าวอ้างที่ควรทดสอบกับข้อมูลของคุณ การจัดเส้นทาง การเรียกเก็บเงิน และข้อผิดพลาดทำงานอย่างไร คุณส่งคำขอไปที่ https://treg.to/call/<tool-id> พร้อมเฮดเดอร์ X-Treg-Token Treg จะค้นหาผู้ให้บริการ เพิ่มข้อมูลรับรองของผู้ให้บริการฝั่งเซิร์ฟเวอร์ และส่งต่อคำตอบของผู้ให้บริการ !Diagram of a Treg call: the coding agent sends a request with the X-Treg-Token header to treg.to/call, which tries providers in a waterfall and returns the provider response plus the X-Treg-Cost-Micro header มีจุดหนึ่งที่เอกสารดูเหมือนขัดแย้งกัน นี่คือวิธีการที่แต่ละส่วนประกอบเข้าข้อยกัน: - เครื่องมือผู้ให้บริการโดยตรง (ตัวอย่างเช่น apollo.people.search) จะไม่มีการสลับไปใช้ตัวสำรอง เอกสารอ้างอิง API ระบุว่า Treg "ไม่จัดเส้นทางระหว่างผู้ให้บริการโดยอัตโนมัติ และไม่สลับไปใช้ตัวสำรอง" คุณเป็นคนเลือกผู้ให้บริการเอง - เครื่องมือที่ถูกจัดเส้นทาง (treg.<capability>) สลับให้ ตามเอกสารอ้างอิง CLI ข้อผิดพลาดจากผู้ให้บริการจะถอยกลับไปยังตัวเลือกถัดไป และเมื่อไม่พบก็จะลองผู้ให้บริการรายถัดไปเช่นกัน โดยเริ่มจากถูกที่สุดก่อน X-Treg-Route-Waterfall: 0 จะหยุดที่การไม่พบครั้งแรก กฎการเรียกเก็บเงิน จาก llms.txt และหน้าค้นหาบุคคล: 1. ทุกการเรียกคิดค่าบริการตามอัตราของผู้ให้บริการจากยอดคงเหลือแบบเติมเงิน โดยบวกเพิ่ม 0% 2. คีย์ผู้ให้บริการของทีมคุณเองจะถูกใช้ก่อนและไม่มีการเรียกเก็บเงิน 3. บัญชีที่ยืนยันใหม่จะได้รับเครดิตฟรี $1.00 หนึ่งครั้ง 4. การไม่พบบนผู้ให้บริการที่คิดต่อความสำเร็จไม่มีค่าใช้จ่าย ผู้ให้บริการบางรายคิดต่อการเรียก ดังนั้นแม้ไม่พบก็อาจมีค่าใช้จ่ายเล็กน้อย 5. ค่าใช้จ่ายจะส่งกลับมาใน X-Treg-Cost-Micro (จำนวนเต็มหน่วยไมโคร-USD) X-Treg-Route-Max-Cost จำกัดเพดานการเรียก บนเครื่องมือที่ถูกจัดเส้นทาง เพดานเริ่มต้นคือ $1 ต่อการเรียก ข้อผิดพลาดแยกออกจากกันอย่างชัดเจน 4xx จากผู้ให้บริการ (นอกเหนือจาก 429) หมายความว่าคำขอของคุณผิด: แก้ไข อย่าลองที่อื่น 429 หรือ 5xx หมายความว่าให้ลองผู้ให้บริการรายถัดไป 402 insufficient_balance หมายความว่าต้องเติมเงิน ตั้งค่า Treg ใน Claude Code หรือ Codex การตั้งค่าเหมือนกันสำหรับเอเจนต์เขียนโค้ดในเครื่องใดก็ได้ (Claude Code, Codex, Cursor, opencode): curl -fsSL https://treg.to/install.sh | sh treg login # browser sign-in: GitHub, Google or an emailed code treg # prints account, team, balance, your own tools, next commands อยากใช้อีเมล? รัน treg login --email you@company.com ได้รับโทเคนจากเพื่อนร่วมทีมมา? curl -fsSL https://treg.to/install.sh | sh -s -- --token "$TREG_TOKEN" จะติดตั้งและลงชื่อเข้าใช้โดยไม่ต้องใช้เบราว์เซอร์ ตัวติดตั้งยังวางสกิล Treg ลงในทุกเอเจนต์ที่ตรวจพบ ดังนั้น Claude Code และ Codex จะเรียนรู้ลูปการค้นหา อ่าน เรียก ได้เอง ไซต์ของ Treg โปรโมตเวอร์ชันบรรทัดเดียวที่คุณวางลงในเอเจนต์ได้เลย: set up treg - https://treg.to/llms.txt ไฟล์นั้นยังขอให้เอเจนต์เลือกใช้ Treg และกดดาวให้รีโป ดังนั้นอ่านสิ่งที่เอเจนต์ของคุณเสนอก่อนอนุมัติ ใช้ claude.ai หรือ ChatGPT แทนหรือไม่? ไม่ต้องติดตั้งอะไร เพิ่ม https://treg.to/mcp/ เป็นคอนเน็กเตอร์แบบกำหนดเอง ทำการยินยอม OAuth ให้เสร็จ และเลือกทีมที่จ่ายเงิน เซิร์ฟเวอร์ MCP เปิดเผย catalog_search, catalog_get, call, balance และอื่น ๆ อีกเล็กน้อย ค้นหา เสริมข้อมูล ตรวจสอบ: พรอมต์สำหรับเอเจนต์สามแบบ แต่ละพรอมต์ระบุงาน ไม่ใช่ระบุผู้ขาย !Pipeline diagram: people.search finds who runs platform at a company, people.email.find returns a best-match work email, people.email.verify returns valid, invalid or catch_all, with an Apidog CLI regression run below checking status 200, cost under cap and verdict present 1. ค้นหาบุคคล Use treg to find the platform and infrastructure leads at modal.com. Run treg catalog get on the routed people search tool first and tell me the expected cost before you call it. List name, title and profile URL. เอเจนต์รันลูป CLI: treg catalog search "find people at a company" treg catalog get treg.people.search treg call treg.people.search --method POST --data '{"company_domain":"modal.com","title":"platform"}' catalog get พิมพ์แผนที่จัดอันดับ ราคา และบรรทัดคำสั่งเรียกที่พร้อมใช้ก่อนที่คุณจะเสียเงินอะไร คำตอบจะกลับมาเป็น {output, raw, _treg} โดยที่ output.people เก็บแถวข้อมูลของผู้ให้บริการ และ _treg.served_by บอกว่าใครเป็นผู้ตอบ รายการ people ที่ว่างเปล่านับเป็นไม่พบ 2. ค้นหาและเสริมข้อมูลอีเมล For each person you found, use treg to find their work email at modal.com. Cap each call at $0.05, and flag any hit where the domain doesn't match. treg call treg.people.email.find --method POST \ --data '{"full_name":"Jane Doe","domain":"modal.com"}' \ --header "X-Treg-Route-Max-Cost: 0.05" คอยดู _treg.domain_match คู่มือสกิลเตือนว่าผู้ให้บริการที่ใช้เฉพาะ LinkedIn มักคืนที่อยู่ของนายจ้างคนก่อน และการพบนั้นยังถูกเรียกเก็บเงิน ต้องการบริบทของบริษัทด้วยหรือไม่? เพิ่ม treg call treg.companies.enrich พร้อมโดเมน เพลย์บุ๊ก GTM ของ Treg แสดงการเรียกนั้นในรูปแบบ POST 3. ตรวจสอบก่อนที่ใครจะส่ง Verify every email you found with treg. Report the verdict per address and drop anything invalid or catch-all. treg call treg.people.email.verify --method POST --data '{"email":"jane@modal.com"}' เครื่องมือตรวจสอบที่ถูกจัดเส้นทางคืนค่า valid, status และ score คุณยังสามารถรวมการตรวจสอบเข้ากับขั้นตอนที่ 2 ได้: ส่ง X-Treg-Route-Verify: true ไปกับ email find แล้วอ่าน _treg.verification.verdict (valid, invalid, catch_all, risky หรือ unknown) การตรวจสอบมีค่าใช้จ่ายเล็กน้อยของตัวเอง และการไม่พบจะไม่ถูกตรวจสอบเลย การรันหนึ่งครั้งมีค่าใช้จ่ายเท่าไร? Treg เผยแพร่ใบเสร็จหนึ่งใบจากวันที่ 23 กันยายน 2026: บุคคลที่ระบุชื่อ 27 คน พบอีเมล 21 ฉบับ ตรวจสอบว่าส่งถึงได้ 20 ฉบับ รวม $0.58 โดยการไม่พบอยู่ที่ $0.00 เรียก Treg API ผ่าน HTTP แบบดิบ เอเจนต์เป็นทางเลือก ไม่บังคับ ทุกการเรียก CLI สอดคล้องกับการเรียก HTTP หนึ่งครั้ง ดังนั้นคุณสามารถเขียนสคริปต์ไปป์ไลน์เดียวกันในภาษาใดก็ได้ curl -X POST "https://treg.to/call/treg.people.email.find" \ -H "X-Treg-[REDACTED CREDENTIAL] \ -H "content-type: application/json" \ -H "X-Treg-Route-Max-Cost: 0.05" \ -d '{"full_name":"Jane Doe","domain":"modal.com"}' \ -D - -D - พิมพ์เฮดเดอร์ตอบกลับ ซึ่งเป็นที่อยู่ของ X-Treg-Cost-Micro และ X-Treg-Served-By มีสี่กฎที่ช่วยให้สคริปต์ไม่พบปัญหา: - อย่าใส่โทเคนใน [REDACTED CREDENTIAL] เด็ดขาด** [เอกสารอ้างอิง API](https://treg.to/docs) ระบุว่า REST ไม่สนใจมัน และ /call/` จะส่งต่อเฮดเดอร์นั้นไปยังผู้ให้บริการ มีเพียงปลายทาง MCP เท่านั้นที่อ่าน Bearer [REDACTED] - **โทเคนส่วนตัวต้องมีทีม โทเคนลงชื่อเข้าใช้ยังต้องมี X-Treg-Org: <team-slug> ด้วย โทเคนของทีมและเอเจนต์มีทีมของมันอยู่แล้ว - เส้นทางแค็ตตาล็อกเป็นสาธารณะ GET https://treg.to/catalog/search?q=verify%20email ทำงานได้โดยไม่ต้องมีโทเคน ซึ่งมีประโยชน์สำหรับตรวจสอบ id ใน CI - คำตอบเป็นของผู้ให้บริการ บนเครื่องมือผู้ให้บริการโดยตรง Treg ส่งต่อเนื้อความตามต้นฉบับ ดังนั้นรูปร่างจึงเปลี่ยนไปตามผู้ให้บริการ เครื่องมือที่ถูกจัดเส้นทางเพิ่มออบเจกต์ output ที่ถูกทำให้เป็นมาตรฐานไว้ด้านบน เก็บความลับให้ห่างจากโค้ด เก็บ TREG_TOKEN ไว้ในที่เก็บความลับ (ดูแนวปฏิบัติที่ดีที่สุดในการจัดการคีย์ API เหล่านี้) ให้เอเจนต์ของคุณทดสอบด้วย Apidog CLI เมื่อการติดต่อสื่อสารขึ้นอยู่กับการเรียกเหล่านี้ การเปลี่ยนแปลงที่เงียบงันก็สร้างความเสียหายได้: ผู้ให้บริการสลับกัน ค่าใช้จ่ายคืบคลานขึ้น หรือฟิลด์คำตัดสินหายไป เอเจนต์ของคุณสามารถป้องกันสิ่งนั้นด้วยชุดการทดสอบถดถอยใน Apidog CLI ตั้งค่า CLI และสกิลเอเจนต์ของมันหนึ่งครั้ง: npm install -g apidog-cli@latest apidog login --with-token <YOUR_APIDOG_TOKEN> npx -y skills add https://apidog.com # pick Claude Code or Codex when prompted จากนั้นให้พรอมต์หนึ่งข้อกับเอเจนต์ของคุณ: Write an OpenAPI 3 file for three Treg calls: POST /call/treg.people.search, POST /call/treg.people.email.find and POST /call/treg.people.email.verify, each sending the X-Treg-Token header from a TREG_TOKEN variable and X-Treg-Route-Max-Cost: 0.05. Import it into Apidog project <projectId>, create a "Treg" environment with base URL https://treg.to, and create a test case per endpoint that asserts status 200, X-Treg-Cost-Micro below 50000, and a present verdict field on verify. Run them and summarize any failures. เอเจนต์อ่านสคีมาของ payload ตรวจสอบ JSON ของตัวเอง แล้วรันคำสั่งเช่นเหล่านี้: apidog import --project <projectId> --format openapi --file ./treg-openapi.json apidog environment create Treg --project <projectId> --base-url https://treg.to apidog cli-schema get test-case-create apidog cli-schema validate test-case-create --file ./find-email-case.json apidog test-case create --project <projectId> --file ./find-email-case.json apidog run --test-case <caseId> --project <projectId> -e <envId> \ --env-var "TREG_TOKEN=$TREG_TOKEN" -r cli,junit ทุกการรันใช้เงินคงเหลือจริง ดังนั้นให้จำกัดชุดการทดสอบไว้ที่สามเคสโดยใช้อินพุตทดสอบที่รู้จัก และตั้งเวลาให้รันทุกวัน ไม่ใช่ทุกคอมมิต บรรทัด apidog run ... -r junit เดียวกันนี้ใส่ลงในไปป์ไลน์ได้ โดยคู่มือ Apidog CLI CI/CDมีตัวอย่าง GitHub Actions และ GitLab สำหรับการตั้งค่าเฉพาะเอเจนต์ ดูที่ Apidog CLI ใน Claude Code หรือ Apidog CLI ใน Codex แผนฟรีครอบคลุมผู้ใช้สูงสุด 4 คน สรุป Treg people search API เปลี่ยนการเสริมข้อมูลลีดให้เป็นการเรียกที่ถูกจัดเส้นทางสามครั้ง: ค้นหา, ค้นหาอีเมล, ตรวจสอบ ตรวจสอบราคาด้วย treg catalog get จำกัดการเรียกด้วย X-Treg-Route-Max-Cost ตรวจสอบทุกที่อยู่ และป้องกันการเรียกเหล่านั้นด้วยการรันทดสอบถดถอย Apidog CLI สำหรับเครื่องมือเอเจนต์เพิ่มเติม เซิร์ฟเวอร์ MCP ชั้นนำสำหรับ Claude Code และบทเรียนการทดสอบ API ที่ขับเคลื่อนด้วยเอเจนต์นี้เป็นบทอ่านต่อไปที่ดี {% embed youtube.com %} คำถามที่พบบ่อย Treg people search API ฟรีหรือไม่? ไม่ทั้งหมด บัญชีที่ยืนยันใหม่จะได้รับเครดิต $1.00 หนึ่งครั้ง การไม่พบบนผู้ให้บริการที่คิดต่อความสำเร็จไม่มีค่าใช้จ่าย และบางเส้นทางเป็นแบบสาธารณะฟรี (แผน verify อีเมลระบุผู้ให้บริการที่ $0 เป็นอันดับแรกเมื่อวันที่ 3 พฤศจิกายน 2026) ทุกอย่างอื่นคิดค่าบริการต่อการเรียกจากยอดคงเหลือแบบเติมเงินในอัตราของผู้ให้บริการ ฉันต้องมีบัญชี Apollo หรือ Hunter เพื่อใช้ Treg ไหม? ไม่ Treg เรียกผู้ให้บริการในบัญชีของตัวเองและเรียกเก็บเงินคุณต่อการเรียก หากทีมของคุณจ่ายให้ผู้ให้บริการอยู่แล้ว ให้ลงทะเบียนคีย์นั้นกับ Treg และการเรียกเหล่านั้นจะใช้คีย์นั้นและไม่ถูกเรียกเก็บเงิน Treg สลับไปใช้ผู้ให้บริการรายอื่นหรือไม่? เฉพาะบนเครื่องมือ treg.* ที่ถูกจัดเส้นทางเท่านั้น พวกมันจะถอยไปยังผู้ให้บริการรายถัดไปเมื่อเกิดข้อผิดพลาดหรือไม่พบ โดยเริ่มจากถูกที่สุดก่อน ภายใต้ X-Treg-Route-Max-Cost เครื่องมือผู้ให้บริการโดยตรงจะไม่สลับผู้ให้บริการให้คุณเลย ฉันจะรู้ได้อย่างไรว่าการเรียกหนึ่งครั้งมีค่าใช้จ่ายเท่าไร? อ่านเฮดเดอร์ตอบกลับ X-Treg-Cost-Micro (ไมโคร-USD) หรือ cost_usd ผ่าน MCP treg balance แสดงยอดคงเหลือและค่าใช้จ่ายล่าสุดของคุณ ฉันใช้ Treg โดยไม่มี Claude Code หรือ Codex ได้ไหม? ได้ ใช้ CLI จากเชลล์ใดก็ได้ เรียก https://treg.to/call/<tool-id> ผ่าน HTTP ด้วย X-Treg-Token หรือเชื่อมต่อ https://treg.to/mcp/ กับ claude.ai หรือ ChatGPT เป็นคอนเน็กเตอร์แบบกำหนดเอง

Treg People Search API 사용법 Treg 인물 검색 API는 코딩 에이전트에게 사람 찾기, 그들의 업무용 이메일, 그리고 그 이메일이 실제로 존재하는지에 대한 판정을 위한 토큰 하나를 제공합니다. treg CLI를 설치하고 한 번 로그인하면, Claude Code나 Codex가 treg.people.search, treg.people.email.find, treg.people.email.verify 같은 라우팅 도구를 호출합니다. Treg는 제공자를 선택하고, 자체 서버에서 제공자의 키를 주입하며, 각 호출을 제공자의 자체 요율로 선불 잔액에서 청구합니다. {% cta apidog.com %} 지금 Apidog을 사용해 보세요 {% endcta %} 이 가이드는 설정, 세 가지 에이전트 프롬프트(찾기, 보강, 검증), 그 뒤에 있는 원시 HTTP 호출, 그리고 에이전트가 실행하는 Apidog CLI 회귀 스위트를 다룹니다. Treg 인물 검색 API란 무엇인가? Treg는 에이전트를 위한 오픈 소스 도구 카탈로그로, 자체 문서에서는 "모델 대신 에이전트 도구를 위한 OpenRouter"라고 설명합니다. 하나의 기본 URL(https://treg.to)과 하나의 토큰으로 123개 제공자에 걸친 4,100개 이상의 도구에 접근할 수 있습니다. 인물 검색의 경우, 라우팅 도구가 호출마다 제공자를 선택하고, 실패 시 다음 제공자를 시도하며, 모든 호출의 비용을 응답 헤더로 보고합니다. !Treg catalog 인물 검색 쪽은 소규모의 라우팅된 기능 집합입니다. 2026년 11월 3일 공개 카탈로그에 등재된 내용은 다음과 같습니다: | 라우팅 도구 | 기능 | 허용하는 입력 | 지원 제공자 수 | | --- | --- | --- | --- | | treg.people.search | 회사 또는 설명으로 사람을 찾습니다 | q, company_domain, company_domain + title, title, full_name | 26 | | treg.people.email.find | 가장 적합한 업무용 이메일을 반환합니다 | domain + full_name, domain + first_name + last_name, linkedin_url | 30 | | treg.people.email.verify | 메일함이 메일을 수신하는지 확인합니다 | email | 17 | | treg.companies.enrich | 회사의 기업 정보(Firmographics) | 회사 도메인 | 30 | 인물 검색 페이지는 인물 검색에 16개 제공자를 언급하고 있으며, 위 수치는 실시간 카탈로그에서 가져온 것이므로 변동될 수 있습니다. 왜 Apollo나 Hunter 키 대신 집계 서비스를 사용해야 할까요? 두 가지 이유가 있습니다. 에이전트가 제공자 키를 보유하지 않으며, 좌석당이 아니라 답변당 지불합니다. Treg의 페이지는 LessieAI의 People Search Bench(119개 태스크)를 인용합니다. B2B 잠재 고객 발굴 태스크에서 Claude Code 단독은 43%를 정확히 답했고, Treg와 함께 사용한 Claude Code는 78.2%를 정확히 답했습니다. 이는 벤더 자체의 차트이므로, 여러분의 데이터로 검증해볼 만한 주장으로 받아들이세요. 라우팅, 과금, 오류는 어떻게 동작하는가 X-Treg-Token 헤더와 함께 https://treg.to/call/<tool-id>로 요청을 보냅니다. Treg는 제공자를 찾고, 서버 측에서 제공자 자격 증명을 추가한 뒤 제공자의 응답을 중계합니다. !Diagram of a Treg call: the coding agent sends a request with the X-Treg-Token header to treg.to/call, which tries providers in a waterfall and returns the provider response plus the X-Treg-Cost-Micro header 문서상 서로 모순되는 것처럼 보이는 지점이 하나 있는데, 각 요소는 이렇게 맞물립니다: - 직접 제공자 도구(예: apollo.people.search)는 장애 조치를 하지 않습니다. API 레퍼런스에 따르면 Treg는 "제공자 간에 자동으로 라우팅하지 않으며 장애 조치도 하지 않습니다." 제공자는 여러분이 선택합니다. - 라우팅 도구(treg.<capability>)는 다릅니다. CLI 레퍼런스에 따르면 제공자 오류가 발생하면 다음 후보로 폴백하며, 실패(miss)인 경우에도 다음 제공자를 시도하고, 가장 저렴한 것부터 시작합니다. X-Treg-Route-Waterfall: 0은 첫 번째 실패에서 중단합니다. llms.txt와 인물 검색 페이지에 나온 과금 규칙은 다음과 같습니다: 1. 모든 호출은 0% 마진으로, 제공자의 자체 요율에 따라 선불 잔액에서 과금됩니다. 2. 여러분 팀이 보유한 자체 제공자 키가 우선 사용되며, 이 경우 청구되지 않습니다. 3. 새로 인증된 계정에는 1회에 한해 $1.00의 무료 크레딧이 제공됩니다. 4. 성공당 과금 제공자에서의 실패는 비용이 들지 않습니다. 일부 제공자는 호출당 청구하므로, 실패에도 약간의 비용이 들 수 있습니다. 5. 청구 금액은 X-Treg-Cost-Micro(정수 마이크로 USD)로 반환됩니다. X-Treg-Route-Max-Cost는 호출 비용 상한을 설정하며, 라우팅 도구의 기본 상한은 호출당 $1입니다. 오류는 명확하게 구분됩니다. 제공자로부터의 4xx(429 제외)는 요청이 잘못되었다는 뜻이므로, 다른 곳에서 재시도하지 말고 수정하세요. 429 또는 5xx는 다음 제공자를 시도하라는 뜻입니다. 402 insufficient_balance는 잔액을 충전하라는 뜻입니다. Claude Code 또는 Codex에서 Treg 설정하기 설정은 모든 로컬 코딩 에이전트(Claude Code, Codex, Cursor, opencode)에서 동일합니다: curl -fsSL https://treg.to/install.sh | sh treg login # browser sign-in: GitHub, Google or an emailed code treg # prints account, team, balance, your own tools, next commands 이메일을 선호하시나요? treg login --email you@company.com을 실행하세요. 팀 동료에게 토큰을 받으셨나요? curl -fsSL https://treg.to/install.sh | sh -s -- --token "$TREG_TOKEN"를 실행하면 브라우저 없이 설치하고 로그인합니다. 설치 프로그램은 또한 감지한 모든 에이전트에 Treg 스킬을 추가하므로, Claude Code와 Codex가 검색, 읽기, 호출 루프를 스스로 학습합니다. Treg 사이트에서는 에이전트에 그대로 붙여넣을 수 있는 한 줄짜리 버전을 소개합니다: set up treg - https://treg.to/llms.txt 해당 파일은 또한 에이전트에게 Treg를 우선 사용하고 저장소에 스타를 누르도록 요청하기도 하므로, 승인하기 전에 에이전트가 제안하는 내용을 읽어보세요. 대신 claude.ai나 ChatGPT를 사용하시나요? 아무것도 설치할 필요가 없습니다. https://treg.to/mcp/를 사용자 지정 커넥터로 추가하고, OAuth 동의를 완료한 뒤 결제할 팀을 선택하세요. MCP 서버는 catalog_search, catalog_get, call, balance 등을 제공합니다. 찾기, 보강, 검증: 세 가지 에이전트 프롬프트 각 프롬프트는 벤더가 아니라 작업을 지정합니다. !Pipeline diagram: people.search finds who runs platform at a company, people.email.find returns a best-match work email, people.email.verify returns valid, invalid or catch_all, with an Apidog CLI regression run below checking status 200, cost under cap and verdict present 1. 인물 찾기. Use treg to find the platform and infrastructure leads at modal.com. Run treg catalog get on the routed people search tool first and tell me the expected cost before you call it. List name, title and profile URL. 에이전트는 CLI 루프를 실행합니다: treg catalog search "find people at a company" treg catalog get treg.people.search treg call treg.people.search --method POST --data '{"company_domain":"modal.com","title":"platform"}' catalog get은 비용을 지출하기 전에 순위가 매겨진 계획, 가격, 바로 사용할 수 있는 호출 라인을 출력합니다. 응답은 {output, raw, _treg} 형태로 반환되며, output.people에는 제공자의 행이, _treg.served_by에는 응답한 제공자 이름이 담깁니다. people 목록이 비어 있으면 실패로 간주됩니다. 2. 이메일 찾기 및 보강. For each person you found, use treg to find their work email at modal.com. Cap each call at $0.05, and flag any hit where the domain doesn't match. treg call treg.people.email.find --method POST \ --data '{"full_name":"Jane Doe","domain":"modal.com"}' \ --header "X-Treg-Route-Max-Cost: 0.05" _treg.domain_match를 확인하세요. 스킬 가이드에서는 LinkedIn 전용 제공자가 이전 직장 주소를 반환하는 경우가 많으며, 그 결과도 여전히 청구된다고 경고합니다. 회사 정보도 필요하신가요? 도메인과 함께 treg call treg.companies.enrich를 추가하세요. Treg의 GTM 플레이북에서 해당 호출의 POST 형식을 볼 수 있습니다. 3. 누군가 발송하기 전에 검증하세요. Verify every email you found with treg. Report the verdict per address and drop anything invalid or catch-all. treg call treg.people.email.verify --method POST --data '{"email":"jane@modal.com"}' 라우팅 검증 도구는 valid, status, score를 반환합니다. 이 검사를 2단계에 통합할 수도 있습니다. 이메일 찾기 요청에 X-Treg-Route-Verify: true를 보내고 _treg.verification.verdict(valid, invalid, catch_all, risky 또는 unknown)를 읽으면 됩니다. 이 검사에는 별도의 소액 비용이 부과되며, 실패한 경우에는 검사하지 않습니다. 실행 비용은 얼마일까요? Treg는 2026년 9월 23일자 영수증 하나를 공개했습니다. 이름이 확인된 인물 27명, 찾은 이메일 21개, 발송 가능으로 검증된 이메일 20개, 총 $0.58, 실패 비용 $0.00. 원시 HTTP로 Treg API 호출하기 에이전트는 선택 사항입니다. 모든 CLI 호출은 하나의 HTTP 요청에 대응하므로, 어떤 언어로든 동일한 파이프라인을 스크립트로 작성할 수 있습니다. curl -X POST "https://treg.to/call/treg.people.email.find" \ -H "X-Treg-[REDACTED CREDENTIAL] \ -H "content-type: application/json" \ -H "X-Treg-Route-Max-Cost: 0.05" \ -d '{"full_name":"Jane Doe","domain":"modal.com"}' \ -D - -D -는 응답 헤더를 출력하며, 여기에 X-Treg-Cost-Micro와 X-Treg-Served-By가 있습니다. 스크립트에 문제가 생기지 않게 하는 네 가지 규칙이 있습니다: - 토큰을 [REDACTED CREDENTIAL] 넣지 마세요.** [API 레퍼런스](https://treg.to/docs)에 따르면 REST는 이를 무시하며, /call/`은 해당 헤더를 제공자에게 전달합니다. 베어러 토큰을 읽는 것은 MCP 엔드포인트뿐입니다. - **개인 토큰에는 팀이 필요합니다. 로그인 토큰에는 X-Treg-Org: <team-slug>도 필요합니다. 팀 토큰과 에이전트 토큰은 팀 정보를 이미 포함하고 있습니다. - 카탈로그 라우트는 공개되어 있습니다. GET https://treg.to/catalog/search?q=verify%20email는 토큰 없이도 작동하므로, CI에서 ID를 확인할 때 편리합니다. - 응답은 제공자의 것입니다. 직접 제공자 도구에서 Treg는 본문을 그대로 중계하므로, 응답 형태는 제공자마다 다릅니다. 라우팅 도구는 그 위에 정규화된 output 객체를 추가합니다. 코드에 비밀 정보를 두지 마세요. TREG_TOKEN은 시크릿 저장소에 보관하세요(이 API 키 관리 모범 사례를 참고하세요). Apidog CLI로 에이전트가 테스트하게 하기 아웃리치가 이러한 호출에 의존하게 되면, 조용한 변경이 문제가 됩니다. 제공자가 교체되거나, 비용이 슬금슬금 올라가거나, 판정 필드가 사라지는 경우입니다. 에이전트는 Apidog CLI의 회귀 스위트로 이를 방지할 수 있습니다. CLI와 에이전트 스킬을 한 번 설정하세요: npm install -g apidog-cli@latest apidog login --with-token <YOUR_APIDOG_TOKEN> npx -y skills add https://apidog.com # pick Claude Code or Codex when prompted 그런 다음 에이전트에 프롬프트 하나를 주세요: Write an OpenAPI 3 file for three Treg calls: POST /call/treg.people.search, POST /call/treg.people.email.find and POST /call/treg.people.email.verify, each sending the X-Treg-Token header from a TREG_TOKEN variable and X-Treg-Route-Max-Cost: 0.05. Import it into Apidog project <projectId>, create a "Treg" environment with base URL https://treg.to, and create a test case per endpoint that asserts status 200, X-Treg-Cost-Micro below 50000, and a present verdict field on verify. Run them and summarize any failures. 에이전트는 페이로드 스키마를 읽고 JSON을 검증한 다음, 다음과 같은 명령을 실행합니다: apidog import --project <projectId> --format openapi --file ./treg-openapi.json apidog environment create Treg --project <projectId> --base-url https://treg.to apidog cli-schema get test-case-create apidog cli-schema validate test-case-create --file ./find-email-case.json apidog test-case create --project <projectId> --file ./find-email-case.json apidog run --test-case <caseId> --project <projectId> -e <envId> \ --env-var "TREG_TOKEN=$TREG_TOKEN" -r cli,junit 실행할 때마다 실제 잔액이 소모되므로, 알려진 테스트 입력을 사용하는 세 개의 케이스로 스위트를 유지하고, 모든 커밋이 아니라 매일 실행하도록 예약하세요. 동일한 apidog run ... -r junit 라인을 파이프라인에 넣을 수 있습니다. Apidog CLI CI/CD 가이드에 GitHub Actions와 GitLab 예제가 있습니다. 에이전트별 설정은 Apidog CLI in Claude Code 또는 Apidog CLI in Codex를 참고하세요. 무료 플랜은 최대 4명의 사용자를 지원합니다. 마무리 Treg 인물 검색 API는 리드 보강을 세 번의 라우팅 호출, 즉 검색, 이메일 찾기, 검증으로 바꿔줍니다. treg catalog get으로 가격을 확인하고, X-Treg-Route-Max-Cost로 호출 비용을 제한하고, 모든 주소를 검증하고, Apidog CLI 회귀 실행으로 호출을 보호하세요. 더 많은 에이전트 도구에 대해서는 Claude Code를 위한 최고의 MCP 서버와 이 에이전트 주도 API 테스트 워크스루가 좋은 다음 읽을거리입니다. {% embed youtube.com %} FAQ Treg 인물 검색 API는 무료인가요? 완전히 무료는 아닙니다. 새로 인증된 계정에는 1회 $1.00의 크레딧이 제공되고, 성공당 과금 제공자에서의 실패는 비용이 들지 않으며, 일부 라우트는 무료 공개 라우트입니다(2026년 11월 3일 이메일 검증 플랜에서는 $0 제공자가 첫 번째로 등재되었습니다). 그 외의 모든 것은 제공자 요율로 선불 잔액에서 호출당 과금됩니다. Treg를 사용하려면 Apollo나 Hunter 계정이 필요한가요? 아닙니다. Treg는 자체 계정으로 제공자를 호출하고 여러분에게 호출당 청구합니다. 팀이 이미 특정 제공자에 비용을 지불하고 있다면, 그 키를 Treg에 등록하면 해당 호출은 그 키를 사용하며 청구되지 않습니다. Treg는 제공자 간에 장애 조치를 하나요? 라우팅된 treg.* 도구에서만 그렇습니다. 오류나 실패 시 X-Treg-Route-Max-Cost 범위 내에서 가장 저렴한 것부터 다음 제공자로 넘어갑니다. 직접 제공자 도구는 절대 제공자를 대신 바꿔주지 않습니다. 호출 비용을 어떻게 알 수 있나요? X-Treg-Cost-Micro 응답 헤더(마이크로 USD)를 읽거나, MCP에서는 cost_usd를 확인하세요. treg balance는 잔액과 최근 지출을 보여줍니다. Claude Code나 Codex 없이 Treg를 사용할 수 있나요? 네. 아무 셸에서나 CLI를 사용하거나, X-Treg-Token과 함께 HTTP로 https://treg.to/call/<tool-id>를 호출하거나, https://treg.to/mcp/를 사용자 지정 커넥터로 claude.ai 또는 ChatGPT에 연결하면 됩니다.

Treg Kişi Arama API'si Nasıl Kullanılır? Treg Kişi Arama API'si Nasıl Kullanılır? Treg people search API'si, kodlama ajanınıza insanları bulmak, iş e-postalarını bulmak ve bu e-postaların gerçek olup olmadığına dair bir hüküm almak için tek bir token verir. treg CLI'sini kurar, bir kez oturum açarsınız; Claude Code ya da Codex, treg.people.search, treg.people.email.find ve treg.people.email.verify gibi yönlendirilmiş araçları çağırır. Treg sağlayıcıyı seçer, sağlayıcının anahtarını kendi sunucusunda enjekte eder ve her çağrıyı sağlayıcının kendi ücreti üzerinden ön ödemeli bakiyeden faturalandırır. {% cta apidog.com %} Bugün Apidog'u deneyin {% endcta %} Bu kılavuz kurulumu, üç ajan istemini (bul, zenginleştir, doğrula), arkalarındaki ham HTTP çağrılarını ve ajanınızın çalıştırdığı bir Apidog CLI regresyon test setini kapsar. Treg people search API'si nedir? Treg, kendi dokümanlarının "modeller yerine ajan araçları için OpenRouter" olarak tanımladığı, ajanlar için açık kaynaklı bir araç kataloğudur. Tek bir temel URL (https://treg.to) ve tek bir token, 123 sağlayıcıdaki 4.100'den fazla araca ulaşır. Kişi aramada, yönlendirilmiş araçlar her çağrı için bir sağlayıcı seçer, ıskalamada bir sonrakini dener ve her çağrının maliyetini bir yanıt başlığında bildirir. !Treg araç kataloğu Kişi arama tarafı küçük bir yönlendirilmiş yetenek setidir. Genel kataloğun 3 Kasım 2026'da listelediği şey şöyleydi: | Yönlendirilmiş araç | Ne yapar | Kabul ettiği girdiler | Arkasındaki sağlayıcılar | | --- | --- | --- | --- | | treg.people.search | Bir şirketteki kişileri veya tanıma göre kişileri bulur | q, company_domain, company_domain + title, title, full_name | 26 | | treg.people.email.find | En iyi eşleşen iş e-postasını döndürür | domain + full_name, domain + first_name + last_name, linkedin_url | 30 | | treg.people.email.verify | Bir posta kutusunun posta kabul edip etmediğini kontrol eder | email | 17 | | treg.companies.enrich | Bir şirket için firma bilgileri | şirket alan adı | 30 | Kişi arama sayfası kişi arama için 16 sağlayıcı belirtiyor; yukarıdaki sayılar canlı katalogdan geliyor, dolayısıyla değişmelerini bekleyin. Neden bir Apollo ya da Hunter anahtarı yerine bir toplayıcıyla uğraşasınız? İki neden. Ajanınız hiçbir zaman bir sağlayıcı anahtarı tutmaz ve koltuk başına değil, yanıt başına ödersiniz. Treg'in sayfası LessieAI'nin People Search Bench'ini (119 görev) alıntılıyor: B2B potansiyel müşteri bulma görevlerinde, tek başına Claude Code %43 doğru yanıt verirken, Treg ile Claude Code %78,2 doğru yanıt verdi. Bu satıcının kendi grafiği, dolayısıyla bunu kendi verinizde test etmeye değer bir iddia olarak görün. Yönlendirme, faturalandırma ve hatalar nasıl çalışır X-Treg-Token başlığıyla https://treg.to/call/<tool-id> adresine bir istek gönderirsiniz. Treg sağlayıcıyı bulur, sağlayıcı kimlik bilgisini sunucu tarafında ekler ve sağlayıcının yanıtını iletir. !Bir Treg çağrısının diyagramı: kodlama ajanı X-Treg-Token başlığıyla treg.to/call adresine bir istek gönderir, bu adres sağlayıcıları bir şelale halinde dener ve sağlayıcı yanıtını X-Treg-Cost-Micro başlığıyla birlikte döndürür Dokümanların çelişiyor gibi göründüğü tek bir nokta var; işte parçaların nasıl bir araya geldiği: - Doğrudan sağlayıcı araçları (örneğin apollo.people.search) yedekleme yapmaz. API referansı, Treg'in "sağlayıcılar arasında otomatik olarak yönlendirme yapmadığını ve yedekleme yapmadığını" söylüyor. Sağlayıcıyı siz seçersiniz. - Yönlendirilmiş araçlar (treg.<capability>) yapar. CLI referansına göre, bir sağlayıcı hatası bir sonraki adaya geri düşer ve bir ıskalama da bir sonraki sağlayıcıyı dener, en ucuzdan başlayarak. X-Treg-Route-Waterfall: 0 ilk ıskalamada durur. Faturalandırma kuralları, llms.txt ve kişi arama sayfasından: 1. Her çağrı, sağlayıcının kendi ücreti üzerinden ön ödemeli bakiyeden, %0 kâr marjıyla ölçülür. 2. Ekibinizin kendi sağlayıcı anahtarı önce kullanılır ve asla faturalandırılmaz. 3. Yeni doğrulanmış hesaplar bir kez 1,00 $ ücretsiz kredi alır. 4. Başarı başına ödeme yapan sağlayıcılardaki ıskalamalar hiçbir şeye mal olmaz; bazı sağlayıcılar çağrı başına faturalandırır, dolayısıyla bir ıskalama yine de biraz tutabilir. 5. Ücret X-Treg-Cost-Micro (tam sayı mikro-USD) olarak geri döner. X-Treg-Route-Max-Cost bir çağrıyı sınırlar; yönlendirilmiş araçlarda varsayılan tavan çağrı başına 1 $'dır. Hatalar net biçimde ayrılır. Sağlayıcıdan gelen bir 4xx (429 dışında) isteğinizin yanlış olduğu anlamına gelir: düzeltin, başka yerde yeniden denemeyin. Bir 429 veya 5xx, bir sonraki sağlayıcıyı deneyin demektir. Bir 402 insufficient_balance, bakiye yükleyin demektir. Treg'i Claude Code veya Codex'te kurun Kurulum herhangi bir yerel kodlama ajanı için aynıdır (Claude Code, Codex, Cursor, opencode): curl -fsSL https://treg.to/install.sh | sh treg login # browser sign-in: GitHub, Google or an emailed code treg # prints account, team, balance, your own tools, next commands E-postayı mı tercih edersiniz? treg login --email you@company.com komutunu çalıştırın. Bir ekip arkadaşınız size bir token mı verdi? curl -fsSL https://treg.to/install.sh | sh -s -- --token "$TREG_TOKEN" tarayıcı olmadan kurar ve oturum açar. Kurucu ayrıca algıladığı her ajana Treg becerisini bırakır, böylece Claude Code ve Codex arama, okuma, çağırma döngüsünü kendi başlarına öğrenir. Treg'in sitesi doğrudan ajana yapıştırabileceğiniz tek satırlık bir sürümü tanıtıyor: set up treg - https://treg.to/llms.txt Bu dosya ayrıca ajanlardan Treg'i tercih etmelerini ve depoya yıldız vermelerini ister, dolayısıyla onaylamadan önce ajanınızın ne önerdiğini okuyun. Onun yerine claude.ai veya ChatGPT mi kullanıyorsunuz? Hiçbir şey kurmayın. https://treg.to/mcp/ adresini özel bir bağlayıcı olarak ekleyin, OAuth onayını tamamlayın ve ödeme yapacak ekibi seçin. MCP sunucusu catalog_search, catalog_get, call, balance ve birkaç şey daha sunar. Bul, zenginleştir, doğrula: üç ajan istemi Her istem işi adlandırır, satıcıyı değil. !İşlem hattı diyagramı: people.search bir şirkette platformu kimin yönettiğini bulur, people.email.find en iyi eşleşen iş e-postasını döndürür, people.email.verify valid, invalid veya catch_all döndürür; altında 200 durumunu, tavanın altındaki maliyeti ve mevcut hükmü kontrol eden bir Apidog CLI regresyon çalıştırması yer alır 1. Kişileri bulun. Use treg to find the platform and infrastructure leads at modal.com. Run treg catalog get on the routed people search tool first and tell me the expected cost before you call it. List name, title and profile URL. Ajan CLI döngüsünü çalıştırır: treg catalog search "find people at a company" treg catalog get treg.people.search treg call treg.people.search --method POST --data '{"company_domain":"modal.com","title":"platform"}' catalog get, herhangi bir şey harcamadan önce sıralanmış planı, fiyatları ve hazır bir çağrı satırını yazdırır. Yanıt {output, raw, _treg} olarak döner; burada output.people sağlayıcının satırlarını tutar ve _treg.served_by kimin yanıtladığını belirtir. Boş bir people listesi ıskalama sayılır. 2. E-postayı bulun ve zenginleştirin. For each person you found, use treg to find their work email at modal.com. Cap each call at $0.05, and flag any hit where the domain doesn't match. treg call treg.people.email.find --method POST \ --data '{"full_name":"Jane Doe","domain":"modal.com"}' \ --header "X-Treg-Route-Max-Cost: 0.05" _treg.domain_match değerine dikkat edin. Beceri kılavuzu, yalnızca LinkedIn üzerinden çalışan bir sağlayıcının sıklıkla eski bir işverenin adresini döndürdüğünü ve bu isabetin yine de faturalandırıldığını uyarır. Şirket bağlamına da mı ihtiyacınız var? Alan adıyla birlikte treg call treg.companies.enrich ekleyin; Treg'in GTM oyun kitabı bu çağrıyı POST biçiminde gösterir. 3. Kimse göndermeden önce doğrulayın. Verify every email you found with treg. Report the verdict per address and drop anything invalid or catch-all. treg call treg.people.email.verify --method POST --data '{"email":"jane@modal.com"}' Yönlendirilmiş doğrulama aracı valid, status ve score döndürür. Kontrolü 2. adıma da katabilirsiniz: e-posta bulma çağrısında X-Treg-Route-Verify: true gönderin ve _treg.verification.verdict değerini okuyun (valid, invalid, catch_all, risky veya unknown). Kontrolün kendi küçük ücreti vardır ve bir ıskalama asla kontrol edilmez. Bir çalıştırma ne kadara mal olur? Treg, 23 Eylül 2026 tarihli bir makbuz yayımlıyor: 27 adlandırılmış kişi, bulunan 21 e-posta, teslim edilebilir olduğu doğrulanan 20 e-posta, toplam 0,58 $, ıskalamalar 0,00 $. Treg API'sini ham HTTP üzerinden çağırın Ajan isteğe bağlıdır. Her CLI çağrısı tek bir HTTP isteğine karşılık gelir, dolayısıyla aynı işlem hattını herhangi bir dilde betikleyebilirsiniz. curl -X POST "https://treg.to/call/treg.people.email.find" \ -H "X-Treg-[REDACTED CREDENTIAL] \ -H "content-type: application/json" \ -H "X-Treg-Route-Max-Cost: 0.05" \ -d '{"full_name":"Jane Doe","domain":"modal.com"}' \ -D - -D - yanıt başlıklarını yazdırır; X-Treg-Cost-Micro ve X-Treg-Served-By buradadır. Dört kural betikleri beladan uzak tutar: - Token'ı asla [REDACTED CREDENTIAL] içine koymayın.** [API referansı](https://treg.to/docs) REST'in bunu yok saydığını ve /call/` adresinin o başlığı sağlayıcıya ilettiğini söylüyor. Yalnızca MCP uç noktası bir Bearer [REDACTED] okur. - **Kişisel token'lar bir ekip gerektirir. Bir oturum açma token'ı ayrıca X-Treg-Org: <team-slug> gerektirir. Ekip ve ajan token'ları zaten kendi ekiplerini taşır. - Katalog rotaları geneldir. GET https://treg.to/catalog/search?q=verify%20email token olmadan çalışır; bu, CI'da kimlikleri kontrol etmek için kullanışlıdır. - Yanıtlar sağlayıcıya aittir. Doğrudan sağlayıcı araçlarında Treg gövdeyi birebir iletir, dolayısıyla biçim sağlayıcıya göre değişir. Yönlendirilmiş araçlar üstüne normalize edilmiş output nesnesini ekler. Sırları koddan uzak tutun. TREG_TOKEN değerini bir sır deposunda saklayın (bu API anahtarı yönetimi en iyi uygulamalarına bakın). Ajanınızın bunu Apidog CLI ile test etmesine izin verin Erişim çalışmaları bu çağrılara bağlı hale geldiğinde, sessiz değişiklikler zarar verir: bir sağlayıcı değişir, maliyetler sinsi sinsi artar veya hüküm alanı kaybolur. Ajanınız bunu Apidog CLI'da bir regresyon test setiyle koruyabilir. CLI'yi ve ajan becerisini bir kez kurun: npm install -g apidog-cli@latest apidog login --with-token <YOUR_APIDOG_TOKEN> npx -y skills add https://apidog.com # pick Claude Code or Codex when prompted Ardından ajanınıza tek bir istem verin: Write an OpenAPI 3 file for three Treg calls: POST /call/treg.people.search, POST /call/treg.people.email.find and POST /call/treg.people.email.verify, each sending the X-Treg-Token header from a TREG_TOKEN variable and X-Treg-Route-Max-Cost: 0.05. Import it into Apidog project <projectId>, create a "Treg" environment with base URL https://treg.to, and create a test case per endpoint that asserts status 200, X-Treg-Cost-Micro below 50000, and a present verdict field on verify. Run them and summarize any failures. Ajan yük şemalarını okur, JSON'unu doğrular, ardından şu gibi komutları çalıştırır: apidog import --project <projectId> --format openapi --file ./treg-openapi.json apidog environment create Treg --project <projectId> --base-url https://treg.to apidog cli-schema get test-case-create apidog cli-schema validate test-case-create --file ./find-email-case.json apidog test-case create --project <projectId> --file ./find-email-case.json apidog run --test-case <caseId> --project <projectId> -e <envId> \ --env-var "TREG_TOKEN=$TREG_TOKEN" -r cli,junit Her çalıştırma gerçek bakiye harcar, dolayısıyla test setini bilinen test girdileriyle üç vakayla sınırlı tutun ve her commit'te değil, günlük olarak zamanlayın. Aynı apidog run ... -r junit satırı bir işlem hattına bırakılır; Apidog CLI CI/CD kılavuzunda GitHub Actions ve GitLab örnekleri var. Ajana özel kurulum için Claude Code'da Apidog CLI veya Codex'te Apidog CLI yazılarına bakın. Ücretsiz plan 4 kullanıcıya kadar kapsar. Toparlarken Treg people search API'si potansiyel müşteri zenginleştirmeyi üç yönlendirilmiş çağrıya dönüştürür: ara, e-posta bul, doğrula. Fiyatları treg catalog get ile kontrol edin, çağrıları X-Treg-Route-Max-Cost ile sınırlayın, her adresi doğrulayın ve çağrıları bir Apidog CLI regresyon çalıştırmasıyla koruyun. Daha fazla ajan aracı için, Claude Code için en iyi MCP sunucuları ve bu ajan odaklı API testi yürütmesi iyi sonraki okumalardır. {% embed youtube.com %} SSS Treg people search API'si ücretsiz mi? Tamamen değil. Yeni doğrulanmış hesaplar bir kez 1,00 $ kredi alır, başarı başına ödeme yapan sağlayıcılardaki ıskalamalar hiçbir şeye mal olmaz ve bazı rotalar ücretsiz genel rotalardır (e-posta doğrulama planı 3 Kasım 2026'da ilk sırada 0 $'lık bir sağlayıcı listeliyordu). Diğer her şey, sağlayıcının ücreti üzerinden ön ödemeli bakiyeden çağrı başına ölçülür. Treg'i kullanmak için bir Apollo veya Hunter hesabına ihtiyacım var mı? Hayır. Treg sağlayıcıyı kendi hesabından çağırır ve sizi çağrı başına faturalandırır. Ekibiniz zaten bir sağlayıcı için ödeme yapıyorsa, o anahtarı Treg'e kaydedin; bu çağrılar onu kullanır ve faturalandırılmaz. Treg sağlayıcılar arasında yedekleme yapar mı? Yalnızca yönlendirilmiş treg.* araçlarında. Bir hata veya ıskalamada, X-Treg-Route-Max-Cost dahilinde, en ucuzdan başlayarak bir sonraki sağlayıcıya geçerler. Doğrudan sağlayıcı araçları sizin için asla sağlayıcı değiştirmez. Bir çağrının ne kadara mal olduğunu nasıl bilirim? X-Treg-Cost-Micro yanıt başlığını (mikro-USD) veya MCP üzerinden cost_usd değerini okuyun. treg balance bakiyenizi ve son harcamalarınızı gösterir. Treg'i Claude Code veya Codex olmadan kullanabilir miyim? Evet. CLI'yi herhangi bir kabuktan kullanın, X-Treg-Token ile https://treg.to/call/<tool-id> adresini HTTP üzerinden çağırın veya https://treg.to/mcp/ adresini özel bir bağlayıcı olarak claude.ai ya da ChatGPT'ye bağlayın.

كيفية استخدام واجهة برمجة تطبيقات Treg للبحث عن الأشخاص؟ كيفية استخدام واجهة برمجة تطبيقات Treg للبحث عن الأشخاص؟ تمنح واجهة برمجة تطبيقات البحث عن الأشخاص من Treg وكيل البرمجة الخاص بك رمزًا واحدًا للعثور على الأشخاص، وبريدهم الإلكتروني للعمل، وحكمًا على ما إذا كانت تلك العناوين حقيقية. تُثبّت أداة سطر الأوامر treg، وتسجّل الدخول مرة واحدة، ثم يستدعي Claude Code أو Codex أدوات موجّهة مثل treg.people.search وtreg.people.email.find وtreg.people.email.verify. يختار Treg المزوّد، ويحقن مفتاح المزوّد على خادمه، ويحاسب على كل استدعاء من رصيد مدفوع مسبقًا بسعر المزوّد نفسه. {% cta apidog.com %} جرّب Apidog اليوم {% endcta %} يغطي هذا الدليل الإعداد، وثلاثة توجيهات للوكيل (البحث، والإثراء، والتحقق)، واستدعاءات HTTP الخام التي تقف خلفها، ومجموعة اختبارات انحدار (regression suite) من Apidog CLI يشغّلها وكيلك. ما هي واجهة برمجة تطبيقات البحث عن الأشخاص من Treg؟ Treg هو كتالوج أدوات مفتوح المصدر للوكلاء، تصفه وثائقه الخاصة بأنه «OpenRouter، لكن لأدوات الوكلاء بدلًا من النماذج». يكفي عنوان أساسي واحد (https://treg.to) ورمز واحد للوصول إلى أكثر من 4,100 أداة عبر 123 مزوّدًا. وفي البحث عن الأشخاص، تختار الأدوات الموجّهة مزوّدًا لكل استدعاء، وتجرّب المزوّد التالي عند عدم العثور على نتيجة، وتُبلّغ عن تكلفة كل استدعاء في ترويسة الاستجابة. !assets.apidog.com جانب البحث عن الأشخاص هو مجموعة صغيرة من القدرات الموجّهة. إليك ما أدرجه الكتالوج العام في 3 نوفمبر 2026: | الأداة الموجّهة | ما تفعله | المدخلات التي تقبلها | المزوّدون خلفها | | --- | --- | --- | --- | | treg.people.search | يجد الأشخاص في شركة ما أو حسب الوصف | q, company_domain, company_domain + title, title, full_name | 26 | | treg.people.email.find | يُرجع أفضل بريد إلكتروني للعمل مطابق | domain + full_name, domain + first_name + last_name, linkedin_url | 30 | | treg.people.email.verify | يتحقق مما إذا كان صندوق البريد يستقبل الرسائل | email | 17 | | treg.companies.enrich | بيانات تعريفية (firmographics) عن شركة | نطاق الشركة (company domain) | 30 | تذكر صفحة البحث عن الأشخاص 16 مزوّدًا للبحث عن الأشخاص؛ أما الأعداد أعلاه فهي من الكتالوج المباشر، لذا توقّع تغيّرها. لماذا تتكبد عناء استخدام وسيط تجميعي بدلًا من مفتاح Apollo أو Hunter؟ لسببين. وكيلك لا يحمل مفتاح مزوّد أبدًا، وأنت تدفع مقابل كل إجابة بدلًا من الدفع لكل مقعد. تستشهد صفحة Treg بمقياس People Search Bench من LessieAI (119 مهمة): في مهام التنقيب B2B الخاصة به، أجاب Claude Code وحده بشكل صحيح بنسبة 43%، بينما أجاب Claude Code مع Treg بنسبة 78.2%. هذا مخطط المورّد نفسه، لذا تعامل معه كادعاء يستحق الاختبار على بياناتك. كيف يعمل التوجيه والفوترة والأخطاء ترسل طلبًا إلى https://treg.to/call/<tool-id> مع الترويسة X-Treg-Token. يعثر Treg على المزوّد، ويضيف بيانات اعتماد المزوّد على جانب الخادم، ويمرّر إجابة المزوّد. !Diagram of a Treg call: the coding agent sends a request with the X-Treg-Token header to treg.to/call, which tries providers in a waterfall and returns the provider response plus the X-Treg-Cost-Micro header هناك نقطة واحدة تبدو الوثائق متناقضة بشأنها، لذا إليك كيف تترابط الأجزاء: - أدوات المزوّد المباشرة (مثل apollo.people.search) لا تنتقل إلى بديل عند الفشل. يقول مرجع الـ API إن Treg «لا يوجّه بين المزوّدين تلقائيًا ولا ينتقل إلى بديل عند الفشل». أنت تختار المزوّد. - الأدوات الموجّهة (treg.<capability>) تفعل ذلك. وفقًا لـ مرجع CLI، يؤدي خطأ المزوّد إلى الرجوع إلى المرشح التالي، كما يؤدي عدم العثور على نتيجة إلى تجربة المزوّد التالي أيضًا، من الأرخص أولًا. القيمة X-Treg-Route-Waterfall: 0 توقف العمل عند أول عدم عثور على نتيجة. قواعد الفوترة، من llms.txt وصفحة البحث عن الأشخاص: 1. يُحتسب كل استدعاء بسعر المزوّد نفسه من رصيد مدفوع مسبقًا، دون أي هامش ربح (0%). 2. يُستخدم مفتاح المزوّد الخاص بفريقك أولًا ولا يُحتسب عليه أي رسم. 3. تحصل الحسابات الموثّقة الجديدة على رصيد مجاني بقيمة 1.00 دولار، مرة واحدة. 4. حالات عدم العثور على نتيجة لدى المزوّدين الذين يحاسبون على النجاح لا تكلف شيئًا؛ لكن بعض المزوّدين يحاسبون على كل استدعاء، لذا قد يكلفك عدم العثور على نتيجة قليلًا. 5. تعود التكلفة في X-Treg-Cost-Micro (عدد صحيح بالميكرو-دولار). وتحدّد X-Treg-Route-Max-Cost سقف الاستدعاء؛ وفي الأدوات الموجّهة يكون السقف الافتراضي دولارًا واحدًا لكل استدعاء. تنقسم الأخطاء بوضوح. رمز 4xx من المزوّد (بخلاف 429) يعني أن طلبك خاطئ: صحّحه، ولا تُعد المحاولة مع مزوّد آخر. أما 429 أو 5xx فيعني تجربة المزوّد التالي. ورمز 402 insufficient_balance يعني أن عليك تعبئة الرصيد. إعداد Treg في Claude Code أو Codex الإعداد متطابق مع أي وكيل برمجة محلي (Claude Code، Codex، Cursor، opencode): curl -fsSL https://treg.to/install.sh | sh treg login # browser sign-in: GitHub, Google or an emailed code treg # prints account, team, balance, your own tools, next commands تفضّل البريد الإلكتروني؟ شغّل treg login --email you@company.com. هل أعطاك زميل رمزًا؟ الأمر curl -fsSL https://treg.to/install.sh | sh -s -- --token "$TREG_TOKEN" يثبّت ويسجّل الدخول دون متصفح. كما يضع المُثبّت مهارة Treg في كل وكيل يكتشفه، لذا يتعلّم Claude Code وCodex حلقة البحث والقراءة والاستدعاء من تلقاء نفسيهما. ويروّج موقع Treg لنسخة من سطر واحد يمكنك لصقها مباشرة في الوكيل: set up treg - https://treg.to/llms.txt يطلب هذا الملف أيضًا من الوكلاء تفضيل Treg وإضافة نجمة إلى المستودع، لذا اقرأ ما يقترحه وكيلك قبل الموافقة عليه. هل تستخدم claude.ai أو ChatGPT بدلًا من ذلك؟ لا تثبّت شيئًا. أضف https://treg.to/mcp/ كموصل مخصّص، وأكمل موافقة OAuth واختر الفريق الذي يدفع. يعرض خادم MCP الأدوات catalog_search وcatalog_get وcall وbalance وعددًا آخر. ابحث، أثرِ، تحقق: ثلاثة توجيهات للوكيل كل توجيه يسمّي المهمة، لا المورّد. !Pipeline diagram: people.search finds who runs platform at a company, people.email.find returns a best-match work email, people.email.verify returns valid, invalid or catch_all, with an Apidog CLI regression run below checking status 200, cost under cap and verdict present 1. ابحث عن الأشخاص. Use treg to find the platform and infrastructure leads at modal.com. Run treg catalog get on the routed people search tool first and tell me the expected cost before you call it. List name, title and profile URL. يشغّل الوكيل حلقة CLI: treg catalog search "find people at a company" treg catalog get treg.people.search treg call treg.people.search --method POST --data '{"company_domain":"modal.com","title":"platform"}' يطبع catalog get الخطة المرتّبة والأسعار وسطر استدعاء جاهزًا قبل أن تنفق أي شيء. تعود الإجابة بصيغة {output, raw, _treg}، حيث تحمل output.people صفوف المزوّد، ويسمّي _treg.served_by من أجاب. وتُعدّ قائمة people الفارغة بمثابة عدم العثور على نتيجة. 2. ابحث عن البريد الإلكتروني وأثرِه. For each person you found, use treg to find their work email at modal.com. Cap each call at $0.05, and flag any hit where the domain doesn't match. treg call treg.people.email.find --method POST \ --data '{"full_name":"Jane Doe","domain":"modal.com"}' \ --header "X-Treg-Route-Max-Cost: 0.05" راقب _treg.domain_match. يحذّر دليل المهارة من أن مزوّدًا يعتمد على LinkedIn فقط كثيرًا ما يُرجع عنوان صاحب عمل سابق، ويُحتسب عليك هذا الناتج رغم ذلك. هل تحتاج سياق الشركة أيضًا؟ أضف treg call treg.companies.enrich مع النطاق؛ ويُظهر دليل GTM الخاص بـ Treg هذا الاستدعاء بصيغة POST. 3. تحقّق قبل أن يرسل أي شخص. Verify every email you found with treg. Report the verdict per address and drop anything invalid or catch-all. treg call treg.people.email.verify --method POST --data '{"email":"jane@modal.com"}' تُرجع أداة التحقق الموجّهة القيم valid وstatus وscore. ويمكنك أيضًا دمج التحقق في الخطوة 2: أرسل X-Treg-Route-Verify: true مع البحث عن البريد واقرأ _treg.verification.verdict (valid أو invalid أو catch_all أو risky أو unknown). وللتحقق رسوم صغيرة خاصة به، ولا يُتحقق أبدًا من حالة عدم العثور على نتيجة. كم تكلّف عملية تشغيل واحدة؟ نشر Treg إيصالًا واحدًا بتاريخ 23 سبتمبر 2026: 27 شخصًا بالاسم، و21 بريدًا إلكترونيًا تم العثور عليه، و20 تم التحقق من إمكانية التسليم إليه، بتكلفة إجمالية 0.58 دولار، وحالات عدم العثور على نتيجة بتكلفة 0.00 دولار. استدعاء واجهة Treg عبر HTTP الخام الوكيل اختياري. كل استدعاء من CLI يقابل طلب HTTP واحد، لذا يمكنك كتابة المسار نفسه بلغة برمجة نصية بأي لغة. curl -X POST "https://treg.to/call/treg.people.email.find" \ -H "X-Treg-[REDACTED CREDENTIAL] \ -H "content-type: application/json" \ -H "X-Treg-Route-Max-Cost: 0.05" \ -d '{"full_name":"Jane Doe","domain":"modal.com"}' \ -D - يطبع -D - ترويسات الاستجابة، وهناك يوجد X-Treg-Cost-Micro وX-Treg-Served-By. أربع قواعد تُبعِد السكربتات عن المتاعب: - لا تضع الرمز أبدًا في [REDACTED CREDENTIAL] يقول [مرجع الـ API](https://treg.to/docs) إن REST يتجاهله، وإن /call/` يمرّر تلك الترويسة إلى المزوّد. نقطة نهاية MCP وحدها هي التي تقرأ رمز bearer. - **الرموز الشخصية تحتاج إلى فريق. يحتاج رمز تسجيل الدخول أيضًا إلى X-Treg-Org: <team-slug>. أما رموز الفريق والوكيل فتحمل فريقها بالفعل. - مسارات الكتالوج عامة. الأمر GET https://treg.to/catalog/search?q=verify%20email يعمل دون رمز، وهو مفيد للتحقق من المعرّفات في CI. - الاستجابات هي استجابات المزوّد. في أدوات المزوّد المباشرة، يمرّر Treg النص كما هو، لذا يتغيّر الشكل بحسب المزوّد. أما الأدوات الموجّهة فتضيف كائن output الموحّد فوقه. أبعِد الأسرار عن الكود. خزّن TREG_TOKEN في مخزن أسرار (راجع أفضل ممارسات إدارة مفاتيح الـ API). دع وكيلك يختبره باستخدام Apidog CLI بمجرد أن تعتمد حملات التواصل على هذه الاستدعاءات، تصبح التغييرات الصامتة مؤذية: تبديل مزوّد، أو تسلّل التكاليف، أو اختفاء حقل الحكم. يستطيع وكيلك حراسة ذلك عبر مجموعة اختبارات انحدار في Apidog CLI. أعدّ أداة CLI ومهارتها للوكيل مرة واحدة: npm install -g apidog-cli@latest apidog login --with-token <YOUR_APIDOG_TOKEN> npx -y skills add https://apidog.com # pick Claude Code or Codex when prompted ثم أعطِ وكيلك توجيهًا واحدًا: Write an OpenAPI 3 file for three Treg calls: POST /call/treg.people.search, POST /call/treg.people.email.find and POST /call/treg.people.email.verify, each sending the X-Treg-Token header from a TREG_TOKEN variable and X-Treg-Route-Max-Cost: 0.05. Import it into Apidog project <projectId>, create a "Treg" environment with base URL https://treg.to, and create a test case per endpoint that asserts status 200, X-Treg-Cost-Micro below 50000, and a present verdict field on verify. Run them and summarize any failures. يقرأ الوكيل مخططات الحِمل (payload schemas)، ويتحقق من صحة JSON الخاص به، ثم يشغّل أوامر كهذه: apidog import --project <projectId> --format openapi --file ./treg-openapi.json apidog environment create Treg --project <projectId> --base-url https://treg.to apidog cli-schema get test-case-create apidog cli-schema validate test-case-create --file ./find-email-case.json apidog test-case create --project <projectId> --file ./find-email-case.json apidog run --test-case <caseId> --project <projectId> -e <envId> \ --env-var "TREG_TOKEN=$TREG_TOKEN" -r cli,junit كل تشغيل ينفق رصيدًا حقيقيًا، لذا أبقِ المجموعة على ثلاث حالات بمدخلات اختبار معروفة وجدولها يوميًا، لا عند كل إيداع (commit). ويُدرج سطر apidog run ... -r junit نفسه في أي مسار أتمتة؛ ويحتوي دليل Apidog CLI لأتمتة CI/CD على أمثلة لـ GitHub Actions وGitLab. لإعدادات خاصة بالوكيل، راجع Apidog CLI في Claude Code أو Apidog CLI في Codex. تغطي الخطة المجانية ما يصل إلى 4 مستخدمين. الخاتمة تحوّل واجهة برمجة تطبيقات البحث عن الأشخاص من Treg إثراء العملاء المحتملين إلى ثلاثة استدعاءات موجّهة: البحث، والعثور على البريد الإلكتروني، والتحقق. تحقّق من الأسعار عبر treg catalog get، وضع سقفًا للاستدعاءات عبر X-Treg-Route-Max-Cost، وتحقق من كل عنوان، واحمِ الاستدعاءات بتشغيل انحدار من Apidog CLI. لمزيد من أدوات الوكلاء، يُعدّ أفضل 10 خوادم MCP لـ Claude Code وهذا الشرح العملي لاختبار الـ API بقيادة الوكيل قراءتين تاليتين جيدتين. {% embed youtube.com %} الأسئلة الشائعة هل واجهة برمجة تطبيقات البحث عن الأشخاص من Treg مجانية؟ ليست مجانية بالكامل. تحصل الحسابات الموثّقة الجديدة على رصيد بقيمة 1.00 دولار مرة واحدة، وحالات عدم العثور على نتيجة لدى المزوّدين الذين يحاسبون على النجاح لا تكلف شيئًا، وبعض المسارات عامة ومجانية (فقد أدرجت خطة التحقق من البريد مزوّدًا بسعر 0 دولار في المرتبة الأولى في 3 نوفمبر 2026). وكل ما عدا ذلك يُحتسب لكل استدعاء من رصيد مدفوع مسبقًا بسعر المزوّد. هل أحتاج إلى حساب Apollo أو Hunter لاستخدام Treg؟ لا. يستدعي Treg المزوّد من حسابه الخاص ويحاسبك على كل استدعاء. وإذا كان فريقك يدفع بالفعل لمزوّد ما، فسجّل ذلك المفتاح لدى Treg وستُستخدم تلك الاستدعاءات له دون أن تُحتسب عليك. هل ينتقل Treg إلى مزوّد بديل عند الفشل؟ فقط في الأدوات الموجّهة treg.*. فهي تنتقل إلى المزوّد التالي عند حدوث خطأ أو عدم العثور على نتيجة، من الأرخص أولًا، ضمن حدود X-Treg-Route-Max-Cost. أما أدوات المزوّد المباشرة فلا تبدّل المزوّد نيابة عنك أبدًا. كيف أعرف تكلفة الاستدعاء؟ اقرأ ترويسة الاستجابة X-Treg-Cost-Micro (بالميكرو-دولار)، أو cost_usd عبر MCP. ويعرض treg balance رصيدك وإنفاقك الأخير. هل يمكنني استخدام Treg دون Claude Code أو Codex؟ نعم. استخدم أداة CLI من أي صدفة (shell)، أو استدعِ https://treg.to/call/<tool-id> عبر HTTP مع X-Treg-Token، أو صِل https://treg.to/mcp/ بـ claude.ai أو ChatGPT كموصل مخصّص.

Ferramentas para seu agent superdesigndev/treg t.co

Treg open source aeo toolkit: superdesigndev/treg Star ⭐️ for updates

@treg_ai Webaccess skill: superdesigndev/treg

People search for Claude just got a lot cheaper. This open-source tool claims: •⁠ ⁠$0.0089 per lead •⁠ ⁠#1 on People Search Bench •⁠ ⁠0% markup •⁠ ⁠Fully open source Try it here: ⁠ treg.to ⁠ Repo: superdesigndev/treg x.com

this is pretty cool. check out : superdesigndev/treg

Treg: OpenRouter for Agent Tools—How a Unified Proxy Turns Thousands of APIs Into Pay-Per-Call Endpoints Agents need dozens of APIs for real work. Semrush costs $139/month, Crunchbase $99, Apollo $59 per seat. Most teams do not buy those subscriptions for a single agent call. Treg (4,779 stars, trending #8 on GitHub Python) solves this by acting as OpenRouter for tools: one base URL, one token, thousands of endpoints priced per call from a cent. The architecture is a relay proxy with server-side credential injection. You point an agent at treg.to, it searches the catalog for "backlink data" or "company enrichment," reads the price, and calls. The proxy injects the upstream API key, OAuth token, or CLI credential without modeling the provider's schema. Your agent never holds the secret. If your team owns a key for the same provider, that key wins and the call is never metered. The Two-Tool Model Treg splits tools into catalog and team-owned. Catalog tools are endpoints Treg serves with its own key or through a verified public route. The proxy holds the provider account. You pay per call from a prepaid balance. New verified accounts get $1.00 free credit once. No provider signup required. Team-owned tools are anything a teammate registered: a paid API account, an OAuth connection, a vendor CLI binary (stripe, gh, vercel), or a SKILL.md recipe. Own-key calls always win over catalog keys and are never metered. The proxy injects the credential at runtime but does not bill for the call. This split solves the cold-start problem. An agent can call Semrush without a Semrush account. If your team later buys a Semrush subscription, you register the key once and every teammate's agent uses it automatically. Credential Injection Without Modeling The proxy relays requests without modeling the upstream API. It does not parse query parameters, body schemas, or response shapes. It only knows where to inject the credential. Each endpoint has one or more bindings. A binding is a rule that says "inject this secret into this part of the request." Examples: - Bearer token in Authorization header - API key in X-API-Key header - Developer token in developer-token header - Query parameter api_key A single request can carry multiple bindings. An endpoint that needs both OAuth and a developer token gets both injected server-side. The caller sends a generic request to Treg. The proxy looks up the bindings, fetches the secrets from its vault, injects them, and forwards the request upstream. This design survives upstream API changes. If a provider renames a parameter or adds a new auth header, you update the binding. The agent code does not change. CLI Execution with Credential Injection CLI tools like stripe, gh, and vercel are first-class citizens. The proxy does not wrap them in a REST API. It runs the vendor binary directly and injects the credential at runtime. When an agent calls a CLI tool, Treg: 1. Looks up the registered CLI and its credential binding 2. Fetches the secret from the vault 3. Spawns the vendor binary with the credential injected as an environment variable or config file 4. Captures stdout and stderr 5. Returns the output to the agent The vendor binary runs unmodified. This avoids the maintenance burden of wrapping every CLI in a custom API. It also means the agent gets the exact output the CLI produces, including error messages and formatting. The credential never leaves the server. The agent sends a request like POST /cli/stripe/customers/list. The proxy runs stripe customers list with the team's Stripe key and returns the JSON. Metering and Billing Boundaries The metering boundary is simple: catalog calls use the prepaid balance, own-key calls do not. When an agent calls an endpoint, the proxy checks if the team has a registered key for that provider. If yes, it uses the team's key and does not meter. If no, it uses the catalog key and deducts the call price from the team's balance. The price is set per endpoint, not per provider. A Semrush backlink call might cost $0.05, a Crunchbase company lookup $0.02, a scraping call $0.01. The catalog lists the price before the call. The agent can decide whether to proceed. The $1.00 free credit is a one-time grant when a verified account creates an eligible team. This prevents abuse while allowing anonymous verified calls. The credit is not renewable. Once spent, the team must add funds. Endpoint Binding Model An endpoint is a base_url plus one or more bindings. A binding specifies: - Secret name: the key in the vault - Injection target: where to put the secret (header, query param, body field, env var) - Injection format: raw string, bearer token, basic auth, custom template Example binding for a provider that needs both OAuth and a developer token: { "endpoint_id": "semrush_backlinks", "base_url": "https://api.semrush.com/analytics/v1", "bindings": [ { "secret_name": "semrush_oauth_token", "target": "header", "header_name": "Authorization", "format": "Bearer {secret}" }, { "secret_name": "semrush_developer_token", "target": "header", "header_name": "developer-token", "format": "{secret}" } ] } When an agent calls this endpoint, the proxy fetches both secrets, injects them into the headers, and forwards the request. The agent only sees the Treg URL and token. State Management and Observability Treg does not manage agent state. It is a stateless proxy. Each call is independent. The agent is responsible for maintaining conversation context, tool call history, and retry logic. Observability is per-call. The proxy logs: - Request timestamp - Endpoint ID - Team ID - Upstream response time - Upstream status code - Metered cost (if catalog call) - Error details (if failed) These logs feed a dashboard that shows per-team usage, per-endpoint latency, and per-provider error rates. The dashboard does not expose upstream API responses. It only shows metadata. The proxy does not retry failed calls. If the upstream returns 500, the agent gets 500. If the upstream times out, the agent gets a timeout. Retry logic belongs in the agent orchestration layer, not the proxy. Security Boundaries The proxy enforces three boundaries: 1. Credential isolation: secrets are scoped to teams. A team cannot access another team's keys. 2. Catalog key protection: catalog keys are never exposed to callers. The proxy injects them server-side. 3. Rate limiting: per-team and per-endpoint rate limits prevent abuse. The vault is a separate service. The proxy requests secrets on demand and does not cache them in memory. Secrets are encrypted at rest and in transit. The proxy does not validate upstream API responses. It relays them as-is. This means a malicious upstream could return arbitrary data. The agent must validate responses before acting on them. Deployment Shape Treg is self-hostable. The reference deployment is a Python service with: - FastAPI for the HTTP layer - PostgreSQL for endpoint metadata and team state - Redis for rate limiting - A vault service (HashiCorp Vault or AWS Secrets Manager) The proxy is stateless and horizontally scalable. Each instance can serve any request. The vault is the only stateful component. The catalog is a JSON file or database table. Each entry is an endpoint with bindings, pricing, and metadata. The catalog can be updated without restarting the proxy. The live instance at treg.to runs on AWS with: - ALB for ingress - ECS Fargate for the proxy - RDS PostgreSQL for metadata - ElastiCache Redis for rate limiting - Secrets Manager for the vault Likely Failure Modes | Failure | Impact | Mitigation | |---------|--------|------------| | Upstream API change | Binding injects credential into wrong field, call fails | Monitor upstream error rates, update bindings, notify teams | | Vault unavailable | Proxy cannot fetch secrets, all calls fail | Vault HA, fallback to cached secrets with short TTL | | Catalog key rate limit | Catalog calls fail, own-key calls unaffected | Per-endpoint rate limits, fallback to own-key if available | | Prepaid balance exhausted | Catalog calls fail, own-key calls unaffected | Balance alerts, auto-reload option | | CLI binary missing | CLI calls fail | Pre-install CLIs in container image, version pinning | | Malicious upstream response | Agent acts on bad data | Agent must validate responses, proxy does not inspect payloads | The biggest operational risk is upstream API changes. The proxy does not model the upstream, so it cannot detect schema changes. If a provider renames a required parameter, calls fail until the binding is updated. The mitigation is monitoring and fast binding updates. The second risk is vault availability. If the vault is down, the proxy cannot fetch secrets. The mitigation is vault HA and a short-lived secret cache. The cache is a trade-off: it reduces vault load but increases credential exposure time. Trade-offs vs. Direct API Calls | Dimension | Treg Proxy | Direct API Calls | |-----------|------------|------------------| | Setup time | Zero (catalog) or one-time registration (own-key) | Per-provider signup, key management | | Cost | Per-call from a cent (catalog) or own-key (free) | Monthly subscription or per-call (varies) | | Latency | +50-100ms proxy hop | Direct to provider | | Credential exposure | Server-side only | Client-side or agent-side | | API change impact | Update binding, agent unchanged | Update agent code | | Observability | Centralized per-team dashboard | Per-provider logs | The proxy adds latency. Every call goes through Treg before reaching the upstream. For latency-sensitive workloads, direct calls are faster. For agent workloads where setup time and credential management dominate, the proxy wins. Technical Verdict Use Treg when: - Your agent needs dozens of APIs and you do not want to manage dozens of subscriptions - You want to try a provider without signing up - You need to share credentials across a team without distributing keys - You want centralized observability for all tool calls - You are building a multi-tenant agent platform and need per-team credential isolation Avoid Treg when: - You need sub-100ms latency to the upstream API - You already have all provider subscriptions and credential management solved - You need to inspect or transform upstream responses before they reach the agent - You cannot tolerate a proxy in the critical path - You need to call providers that require client-side OAuth flows (the proxy cannot complete those) The architecture is clean. The relay-without-modeling design avoids the maintenance burden of wrapping every API. The two-tool model solves cold-start and team-sharing problems. The biggest operational challenge is keeping bindings in sync with upstream changes. If you can monitor and update bindings quickly, the proxy is a force multiplier for agent tool access. Source Links - Treg GitHub Repository - Live Instance