generated: '2026-07-25' method: generated source: >- openapi/ (every operationId referenced below was verified verbatim against the harvested specifications) + Airtel's public developer documentation provider_published_skills: false provider_published_note: >- No AGENTS.md, skill file or agent-facing guidance is published by Bharti Airtel on any host. The skills below are generated by API Evangelist from Airtel's own specifications and documentation. skills: - file: bharti-airtel-send-compliant-sms.md name: Send a DLT-compliant SMS with Airtel IQ api: openapi/bharti-airtel-iq-sms-openapi.yml operations: - sendSmsUsingPOST_2 - sendSmsUsingGET - sendSmsUsingPOST - sendSmsViaCsvUsingPOST - sendSmsViaCsvUsingPOST_1 - file: bharti-airtel-locate-device-with-consent.md name: Locate a device with subscriber consent using Airtel Locate api: openapi/bharti-airtel-locate-openapi.yml operations: - getOrCreateOauthTokenUsingPOST_2 - initiateConsentUsingPOST_3 - getConsentUsingGET_2 - searchUsingGET_2 - findAllUsingGET_2 - getLocationUsingGET_3 - patchResourceUsingPATCH_3 - deleteResourceUsingDELETE_3 - addressValidationUsingPOST_1 - file: bharti-airtel-manage-iot-sim-lifecycle.md name: Manage the Airtel IoT SIM lifecycle api: openapi/bharti-airtel-iot-openapi.yml operations: - generateAccessTokenUsingPOST - refreshAccessTokenUsingPOST - fetchCustomerBasketsUsingGET - fetchCustomerSimsUsingGET - fetchCustomerPlansUsingGET_1 - activateTestSimsUsingPOST - activateSimFromTestUsingPOST - activateSimsUsingPOST - changePlanUsingPOST - swapSimUsingPOST - safeCustodyUsingPOST - outOfSafeCustodyUsingPOST - tempDisconnectionUsingPOST - tdResumeUsingPOST - fetchJobsUsingGET - fetchOrdersUsingGET - fetchDeviceInfoUsingGET - fetchDataUsageUsingGET - fetchSimKycDetailsListUsingGET - updateSimKycDetailsUsingPOST not_covered: - api: iq-reporting reason: >- One operation (postSampleCdrUsingPOST), and it is a shape reference for the endpoint the integrator must build rather than an endpoint the integrator calls. Covered in asyncapi/bharti-airtel-webhooks.yml instead. - api: smart-api reason: Legacy, abandoned in place, no harvestable specification to ground a skill in.