> ## Documentation Index
> Fetch the complete documentation index at: https://aisa.one/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> - Base URLs: models `https://api.aisa.one/v1` (Gemini GenerateContent: `https://api.aisa.one/v1beta`); data APIs `https://api.aisa.one/apis/v1`. The `servers` of each operation in https://aisa.one/openapi.yaml is authoritative.
> - Auth: `Authorization: Bearer $AISA_API_KEY`. Never print, log, or commit the key.
> - MCP (preferred for agents): `https://mcp.aisa.one/mcp`, signed in with OAuth, so there is no key to paste.
> - Agent Skill: `npx skills add AIsa-team/agent-skills --skill aisa`. Fallback with the AIsa CLI: `aisa skills install aisa`.
> - Spending: docs, https://aisa.one/models, https://aisa.one/api, `/v1/models`, and MCP `search`, `list_categories`, `get_details`, `batch_quote`, and the `account` operation are free. Quote the exact calls before running them (MCP `batch_quote`, CLI `aisa quote --json`). If the quote reports `auto_execute_eligible: true`, run it unless the user set a tighter limit or asked only for a quote. Otherwise, tell the user in one message the planned calls, the quoted price, and a total USD budget for the task, then wait for approval. Direct HTTP calls follow the stricter rule at https://aisa.one/docs/get-started/cli.md#direct-http-fallback. Do not make paid calls to test availability. Full rule: https://aisa.one/llms.txt

# Find a person's mobile number by profile URL or email

> at least one identifier is required. This is the most expensive endpoint in the file at 5 credits a hit — and mobile numbers are regulated contact data (TCPA / CASL), so treat the result accordingly

<!-- aisa-pricing:start -->
按用量计费；默认请求预估费用：$0.125 USD（不是固定价格）。 声明的单位费率：每 provider_credit $0.000001 USD。 最终费用以账户适用价格及实际结算为准。
<!-- aisa-pricing:end -->

## 请求规范

* **方法与路径:** POST /apis/v1/leadmagic/people-phone-find
* **可用状态:** enabled
* **请求 URL 模板:** `https://api.aisa.one/apis/v1/leadmagic/people-phone-find`
* **Runtime 事实版本:** 5deb1b0a5edc249b6c389685a3ef109ad7e0150396ecbd2b8d4896e17effee94

[完整 OpenAPI 定义](https://aisa.one/docs/reference-contracts/zh/leadmagic.json)

有效请求与价格声明（包括认证和引用的 schema）：

```json theme={null}
{
  "operationId": "leadmagic.people-phone-find",
  "method": "POST",
  "path": "/apis/v1/leadmagic/people-phone-find",
  "servers": [
    {
      "url": "https://api.aisa.one"
    }
  ],
  "parameters": [],
  "security": [
    {
      "bearerAuth": []
    }
  ],
  "requestBody": {
    "required": false,
    "content": {
      "application/json": {
        "schema": {
          "type": "object",
          "properties": {
            "profile_url": {
              "type": "string",
              "description": "professional profile URL",
              "examples": [
                "https://www.linkedin.com/in/example"
              ]
            },
            "work_email": {
              "type": "string",
              "description": "the person's work email"
            },
            "personal_email": {
              "type": "string",
              "description": "the person's personal email"
            }
          }
        }
      }
    }
  },
  "x-aisa-status": "enabled",
  "x-aisa-pricing": {
    "cost_contract": "response_units",
    "customer_multiplier": 1.0,
    "customer_pricing": "provider_cost_multiplier",
    "default_request_estimate_usd": 0.125,
    "estimate_source": "profile_seed",
    "evidence_source": "response_header",
    "unit": "provider_credit",
    "unit_rate_usd": 1e-06
  },
  "components": {
    "securitySchemes": {
      "bearerAuth": {
        "scheme": "bearer",
        "type": "http"
      }
    }
  }
}
```

## 费用与请求规则

按用量计费；默认请求预估费用：\$0.125 USD（不是固定价格）。 声明的单位费率：每 provider\_credit \$0.000001 USD。 最终费用以账户适用价格及实际结算为准。

公开参考值不是你的账户报价或最终扣费。对于支持 X-AISA-Cost-Mode: quote 的接口，执行前请针对完整请求获取免费报价；执行后通过响应费用元数据和 Usage Logs 核对结算费用。1 USD 等于 1,000,000 个整数 micro-USD。

* **默认请求参考估价（USD）:** 0.125
* **声明的单位费率（USD）:** 1e-06
* **计费单位:** provider\_credit
* **计费依据:** response\_units
* **公开参考倍率:** 1.0
* **结算证据来源:** response\_header


## OpenAPI

````yaml reference-contracts/zh/leadmagic.json POST /apis/v1/leadmagic/people-phone-find
openapi: 3.1.0
info:
  description: ''
  title: LeadMagic
  version: '1'
  x-aisa-capabilities:
    idempotency: Idempotency-Key
    max_price: X-AISA-Max-Price-USD
    quote:
      header: X-AISA-Cost-Mode
      value: quote
  x-aisa-configured-paths:
    - /apis/v1/leadmagic/b2b-ads-search
    - /apis/v1/leadmagic/b2b-profile
    - /apis/v1/leadmagic/b2b-profile-email
    - /apis/v1/leadmagic/companies-enrich
    - /apis/v1/leadmagic/companies-search-v3
    - /apis/v1/leadmagic/company-funding
    - /apis/v1/leadmagic/competitors-search
    - /apis/v1/leadmagic/employee-finder
    - /apis/v1/leadmagic/enrich-company-v1
    - /apis/v1/leadmagic/google-ads-search
    - /apis/v1/leadmagic/job-change-detector
    - /apis/v1/leadmagic/jobs-finder
    - /apis/v1/leadmagic/jobs-search-v3
    - /apis/v1/leadmagic/meta-ads-search
    - /apis/v1/leadmagic/people-email-find
    - /apis/v1/leadmagic/people-email-verify
    - /apis/v1/leadmagic/people-enrich
    - /apis/v1/leadmagic/people-phone-find
    - /apis/v1/leadmagic/people-search
    - /apis/v1/leadmagic/personal-email-finder
    - /apis/v1/leadmagic/role-finder
    - /apis/v1/leadmagic/technographics
  x-aisa-document:
    facts_hash: 5deb1b0a5edc249b6c389685a3ef109ad7e0150396ecbd2b8d4896e17effee94
    generator_version: '3'
    protocol_version: '1'
    schema_version: '1'
    composer_version: '28'
    response_pending:
      - operation_id: leadmagic.b2b-ads-search
        path: /apis/v1/leadmagic/b2b-ads-search
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.b2b-profile
        path: /apis/v1/leadmagic/b2b-profile
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.b2b-profile-email
        path: /apis/v1/leadmagic/b2b-profile-email
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.companies-enrich
        path: /apis/v1/leadmagic/companies-enrich
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.companies-search-v3
        path: /apis/v1/leadmagic/companies-search-v3
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.company-funding
        path: /apis/v1/leadmagic/company-funding
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.competitors-search
        path: /apis/v1/leadmagic/competitors-search
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.employee-finder
        path: /apis/v1/leadmagic/employee-finder
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.google-ads-search
        path: /apis/v1/leadmagic/google-ads-search
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.job-change-detector
        path: /apis/v1/leadmagic/job-change-detector
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.jobs-finder
        path: /apis/v1/leadmagic/jobs-finder
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.jobs-search-v3
        path: /apis/v1/leadmagic/jobs-search-v3
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.meta-ads-search
        path: /apis/v1/leadmagic/meta-ads-search
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.people-email-find
        path: /apis/v1/leadmagic/people-email-find
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.people-email-verify
        path: /apis/v1/leadmagic/people-email-verify
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.people-enrich
        path: /apis/v1/leadmagic/people-enrich
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.people-phone-find
        path: /apis/v1/leadmagic/people-phone-find
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.personal-email-finder
        path: /apis/v1/leadmagic/personal-email-finder
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.role-finder
        path: /apis/v1/leadmagic/role-finder
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
      - operation_id: leadmagic.technographics
        path: /apis/v1/leadmagic/technographics
        method: POST
        statuses:
          - '200'
        reason: public success response has no authoritative payload declaration
    document_hash: sha256:8f17e9fc701ee86bc73ff1496bc612e600209192b96a4672ba056cd99d00ef17
  x-aisa-plans:
    builder: 1
    display_plan: payg
    payg: 1
    similarweb_payg: 1
    team: 1
    version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb
  x-aisa-provider: leadmagic
  x-aisa-catalogs:
    leadmagic:
      title: LeadMagic
      description: ''
      x-aisa-document:
        facts_hash: 5deb1b0a5edc249b6c389685a3ef109ad7e0150396ecbd2b8d4896e17effee94
        generator_version: '3'
        protocol_version: '1'
        schema_version: '1'
      x-aisa-plans:
        builder: 1
        display_plan: payg
        payg: 1
        similarweb_payg: 1
        team: 1
        version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb
      x-aisa-capabilities:
        idempotency: Idempotency-Key
        max_price: X-AISA-Max-Price-USD
        quote:
          header: X-AISA-Cost-Mode
          value: quote
servers:
  - url: https://api.aisa.one
security:
  - bearerAuth: []
paths:
  /apis/v1/leadmagic/people-phone-find:
    post:
      tags:
        - LeadMagic
      summary: Find a person's mobile number by profile URL or email
      description: >-
        at least one identifier is required. This is the most expensive endpoint
        in the file at 5 credits a hit — and mobile numbers are regulated
        contact data (TCPA / CASL), so treat the result accordingly


        <!-- aisa-pricing:start -->

        按用量计费；默认请求预估费用：$0.125 USD（不是固定价格）。 声明的单位费率：每 provider_credit $0.000001
        USD。 最终费用以账户适用价格及实际结算为准。

        <!-- aisa-pricing:end -->
      operationId: leadmagic.people-phone-find
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                profile_url:
                  type: string
                  description: professional profile URL
                  examples:
                    - https://www.linkedin.com/in/example
                work_email:
                  type: string
                  description: the person's work email
                personal_email:
                  type: string
                  description: the person's personal email
      responses:
        '200':
          description: 成功响应
        default:
          content:
            application/json:
              schema: {}
          description: >-
            Error response; upstream passthrough responses may use provider
            formats
components:
  securitySchemes:
    bearerAuth:
      scheme: bearer
      type: http

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.