canonical: https://jentic.com/apis/bouyguestelecom.fr/bouyguestelecom # Bouyguestelecom Fr rechercher Entite Juridique The Bouygues Telecom legal-entity API resolves the legal entity that handles invoice routing for a partner. Its single operation looks up the routing legal entities so a partner billing system can direct invoices correctly. Requests authenticate with OAuth2 using the authorization code flow. ## For AI agents Look up the legal entity responsible for invoice routing for a Bouygues Telecom partner. ## Scope Does not handle invoice creation, payment, or general company search - use for resolving Bouygues Telecom partner invoice-routing legal entities only. ## Capabilities - Look up the legal entity that handles invoice routing for a partner - Resolve billing routing details for partner invoicing - Retrieve routing legal-entity data over an OAuth2-secured endpoint ## Use cases ### Invoice routing resolution A partner billing system needs to know which legal entity should receive an invoice. The Bouygues Telecom legal-entity API returns the routing legal entities so the partner can address invoices to the correct entity. Example prompt: Call the routing operation and return the legal entity that should receive a partner invoice ### Partner billing onboarding When onboarding a new partner arrangement, a finance team needs to confirm the billing entity structure. The lookup returns the routing legal entities so onboarding can record the correct target before invoices flow. Example prompt: Retrieve the routing legal entities and store the correct billing target for a new partner ### AI agent billing lookup An AI agent preparing partner invoices can resolve the correct legal entity without hand-wiring the OAuth2 flow. Through Jentic the agent discovers the lookup by intent and calls it with the stored credential. Example prompt: Search Jentic for 'look up the invoice routing legal entity', load the schema, and resolve the target entity ## Key resources - **Routing legal entities** — Look up the legal entity that handles a partner's invoice routing ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 70 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 53 / 100 - Agent Usability: 94 / 100 - Security: 90 / 100 - AI Discoverability: 50 / 100 - **View full report:** https://jentic.com/apis/bouyguestelecom.fr/bouyguestelecom/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Bouygues Telecom legal-entity API by hand means running the OAuth2 authorization code flow and shaping the routing query yourself. Through Jentic you install once, import the API from the API Directory, store your credential once, and your agent calls it. - **Permission scoping:** The Bouygues Telecom legal-entity API exposes a single read operation, so you limit the agent to that lookup and nothing else. You credit the agent only with the operations you allow, so anything beyond the routing lookup stays out unless you add it. - **Credential handling:** Your the Bouygues Telecom credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'look up the invoice routing legal entity', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing docs. ## Related APIs - **OpenCorporates API** — Company and legal-entity data across many jurisdictions - **UK Companies House API** — Official UK company and legal-entity records - **Clearbit API** — Company enrichment data to augment a resolved entity ## FAQ ### What authentication does the Bouygues Telecom legal-entity API use? The Bouygues Telecom legal-entity API authenticates with OAuth2 using the authorization code flow. Through Jentic the OAuth2 credential is stored encrypted in your own instance and the token is applied at run time. ### Is there a the Bouygues Telecom legal-entity API MCP server? You don't need an MCP server to give your agent the Bouygues Telecom legal-entity API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. That keeps another server's tool definitions out of your agent's context while still giving it the operation set from the spec. ### What does the Bouygues Telecom legal-entity API return? It returns the legal entity that handles invoice routing for a partner, so a billing system can direct each invoice to the correct entity. ### Can I limit what my agent is allowed to do with the Bouygues Telecom legal-entity API? Yes. Because you run Jentic One yourself, your own rules decide which the Bouygues Telecom legal-entity API operations and credentials the agent may use. You grant only the operations it needs, such as looking up a routing entity, so any operation you have not granted stays off limits unless you add it. The choice of what the agent may call is yours. ### How do I connect my agent to the Bouygues Telecom legal-entity API through Jentic? Search Jentic by intent such as 'look up the invoice routing legal entity' to discover the operation, load its input schema, and your agent calls it with your stored credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.