Skip to content
atlasby Aidenix Open account
How Atlas works

Ask a question.
Watch the chain come together.

Follow real Atlas runs from the first MCP call to the source response. The agent gets a recipe. Your tools turn it into a result.

Real responses. Replayed here.

Tesla SEC filings

Company → CIK → filings

Recorded run ·
Agent + your toolsrecorded session
Your question

Find Tesla, Inc. in the United States SEC register and show its CIK, ticker, exchange and recent filings.

  1. 01 Atlas MCPRecorded

    Find the right chain

    aidenix_search

    Atlas matches the question to company-sec-filings.

    Inputs & result summary

    Inputs

    {
      "query": "Find Tesla, Inc. in the United States SEC register and show its CIK, ticker, exchange and recent filings.",
      "top": 1
    }

    Normalized result from recorded responses

    {
      "results": [
        {
          "kind": "chain",
          "id": "company-sec-filings",
          "score": 1.05,
          "rrf": 0.032787,
          "cosine": 0.6320068449334397,
          "via": "retrieve",
          "probe_age_days": null,
          "boosts": {},
          "penalties": {}
        }
      ],
      "params": {
        "company_name": "Tesla, Inc."
      },
      "limitations": [
        "company-sec-filings: partial chain; some steps are unavailable, unverified or require keys; inspect recipe.step_gates and step authentication requirements"
      ]
    }
  2. 02 Atlas MCPRecorded

    Get the recipe

    aidenix_get_recipe

    Source endpoints, inputs and the links between steps arrive in one recipe.

    Inputs & result summary

    Inputs

    {
      "id": "company-sec-filings",
      "runnable": true
    }

    Normalized result from recorded responses

    {
      "id": "company-sec-filings",
      "steps": 2,
      "accepts_params": [
        "company_name"
      ],
      "executable": false,
      "executable_reason": "step 1 (efts.sec.gov#sec-edgar--entity-search): own verification expired"
    }
  3. 03 Your clientRecorded

    Resolve the company

    run_chain_recipe

    Your tools run the recipe. The company name becomes a stable identifier.

    Inputs & result summary

    Inputs

    {
      "seed": {
        "company_name": "Tesla, Inc."
      }
    }

    Normalized result from recorded responses

    {
      "Ticker": "TSLA",
      "Exchange": "Nasdaq",
      "Incorporated in": "TX",
      "Industry": "Motor Vehicles & Passenger Car Bodies",
      "SEC CIK": "1318605"
    }
  4. 04 Source responseRecorded

    Follow the identifier

    GET /submissions/CIK0001318605.json

    The CIK opens the filer profile and its recent filings.

    Inputs & result summary

    Inputs

    {
      "SEC CIK": "1318605"
    }

    Normalized result from recorded responses

    {
      "cik": "1318605",
      "name": "Tesla, Inc.",
      "tickers": [
        "TSLA"
      ],
      "recent_forms": [
        "DEFA14A",
        "SCHEDULE 13G/A",
        "10-Q",
        "8-K",
        "DEFA14A"
      ],
      "recent_filing_dates": [
        "2026-10-29",
        "2026-10-27",
        "2026-10-22",
        "2026-10-21",
        "2026-10-19"
      ]
    }

Your result

Matched chaincompany-sec-filings

2 source steps · Recipe retrieved · Runs in your tools

Company resolved

Tesla, Inc.

SEC CIK1318605
Ticker
TSLA
Exchange
Nasdaq
Incorporated in
TX
Industry
Motor Vehicles & Passenger Car Bodies

Recent filings

Source response

Five filings from the recorded SEC response.

FormFiledDocument
DEFA14A2026-10-29tm267596d8_defa14a.htm
SCHEDULE 13G/A2026-10-27xslSCHEDULE_13G_X02/primary_doc.xml
10-Q2026-10-22tsla-20260930.htm
8-K2026-10-21tsla-20261021.htm
DEFA14A2026-10-19tm267596d7_defa14a.htm

The filing list is a dated excerpt. Open the SEC record for the current filings.

The recorded recipe

The MCP returns the instructions. Your client executes them.

{
  "id": "company-sec-filings",
  "name": "US SEC registrant by company name → CIK → SEC filer profile and recent filings (United States only)",
  "accepts_params": [
    "company_name"
  ],
  "returns_outputs": [
    "cik",
    "sec_name",
    "tickers",
    "exchanges",
    "sic_description",
    "state_of_incorporation",
    "fiscal_year_end",
    "former_names",
    "recent_forms",
    "recent_filing_dates",
    "recent_documents"
  ],
  "executable": false,
  "executable_reason": "step 1 (efts.sec.gov#sec-edgar--entity-search): own verification expired",
  "steps": [
    {
      "step": 1,
      "source": "efts.sec.gov",
      "method": "GET",
      "url": "https://efts.sec.gov/LATEST/search-index",
      "auth": "none"
    },
    {
      "step": 2,
      "source": "data.sec.gov",
      "method": "GET",
      "url": "https://data.sec.gov/submissions/CIK{cik}.json",
      "auth": "none"
    }
  ]
}

The saved catalog checks had expired at capture time. This recording includes a fresh client run; it does not update the catalog verification status.

Tesco Company group

Company → LEI → group

Recorded run ·
Agent + your toolsrecorded session
Your question

Find TESCO PLC's LEI, company registration number and direct subsidiaries from GLEIF.

  1. 01 Atlas MCPRecorded

    Find the right chain

    aidenix_search

    Atlas matches the question to company-group-lei.

    Inputs & result summary

    Inputs

    {
      "query": "Find TESCO PLC's LEI, company registration number and direct subsidiaries from GLEIF.",
      "top": 1
    }

    Normalized result from recorded responses

    {
      "results": [
        {
          "kind": "chain",
          "id": "company-group-lei",
          "score": 1.05,
          "rrf": 0.032522,
          "cosine": 0.551295761761598,
          "via": "retrieve",
          "probe_age_days": null,
          "boosts": {},
          "penalties": {}
        }
      ],
      "params": {
        "company_name": "TESCO PLC"
      },
      "limitations": [
        "company-group-lei: partial chain; some steps are unavailable, unverified or require keys; inspect recipe.step_gates and step authentication requirements"
      ]
    }
  2. 02 Atlas MCPRecorded

    Get the recipe

    aidenix_get_recipe

    Source endpoints, inputs and the links between steps arrive in one recipe.

    Inputs & result summary

    Inputs

    {
      "id": "company-group-lei",
      "runnable": true
    }

    Normalized result from recorded responses

    {
      "id": "company-group-lei",
      "steps": 6,
      "accepts_params": [
        "company_name"
      ],
      "executable": false,
      "executable_reason": "step 1 (api.gleif.org#api.gleif.org-5): own verification expired"
    }
  3. 03 Your clientRecorded

    Resolve the company

    run_chain_recipe

    Your tools run the recipe. The company name becomes a stable identifier.

    Inputs & result summary

    Inputs

    {
      "seed": {
        "company_name": "TESCO PLC"
      }
    }

    Normalized result from recorded responses

    {
      "Company number": "00445790",
      "Jurisdiction": "GB",
      "Identity match": "Exact legal name",
      "Direct-child records returned": "32",
      "Legal entity identifier": "2138002P5RNKC5W2JZ46"
    }
  4. 04 Source responseRecorded

    Follow the identifier

    GET /lei-records/2138002P5RNKC5W2JZ46/direct-children

    32 direct-child records returned. The GLEIF result survives an unavailable optional lookup.

    Inputs & result summary

    Inputs

    {
      "Legal entity identifier": "2138002P5RNKC5W2JZ46"
    }

    Normalized result from recorded responses

    {
      "lei": "2138002P5RNKC5W2JZ46",
      "legal_name": "TESCO PLC",
      "registration_number": "00445790",
      "child_name": [
        "TESCO HOLDINGS LIMITED",
        "TESCO DISTRIBUTION LIMITED",
        "ONE STOP STORES LIMITED",
        "DUNNHUMBY IT SERVICES INDIA PRIVATE LIMITED",
        "TESCO BENGALURU PRIVATE LIMITED"
      ],
      "child_country": [
        "GB",
        "GB",
        "GB",
        "IN",
        "IN"
      ],
      "returned_child_records": 32,
      "parent_match_status": "not_reported_or_unavailable"
    }

Your result

Matched chaincompany-group-lei

6 source steps · Recipe retrieved · Runs in your tools

Company resolved

TESCO PLC

Legal entity identifier2138002P5RNKC5W2JZ46
Company number
00445790
Jurisdiction
GB
Identity match
Exact legal name
Direct-child records returned
32

Direct subsidiaries

Source response

Showing 5 of 32 direct-child records returned by GLEIF.

Legal entityCountryLEI
TESCO HOLDINGS LIMITEDGB213800JBW23QIB8OWZ72
TESCO DISTRIBUTION LIMITEDGB2138004Y2M2KH5911J79
ONE STOP STORES LIMITEDGB213800TY5RDH3FLCEA92
DUNNHUMBY IT SERVICES INDIA PRIVATE LIMITEDIN213800BJ65I2ZRC7IN50
TESCO BENGALURU PRIVATE LIMITEDIN335800TEOS1NYZDSRV44

The optional Wikidata lookup returned HTTP 403; the exact GLEIF match was retained. No ultimate-parent record was returned. This does not establish ultimate beneficial ownership.

The recorded recipe

The MCP returns the instructions. Your client executes them.

{
  "id": "company-group-lei",
  "name": "Company name to LEI, registration authority, ultimate parent and direct subsidiaries",
  "accepts_params": [
    "company_name"
  ],
  "returns_outputs": [
    "child_name",
    "child_lei",
    "child_country",
    "ultimate_parent_name",
    "ultimate_parent_lei",
    "ultimate_parent_country",
    "lei",
    "qid",
    "legal_name",
    "registration_number",
    "registration_authority",
    "registration_jurisdiction",
    "identity_match_status",
    "parent_match_status",
    "parent_reporting_exception_url",
    "candidate_legal_entities"
  ],
  "executable": false,
  "executable_reason": "step 1 (api.gleif.org#api.gleif.org-5): own verification expired",
  "steps": [
    {
      "step": 1,
      "source": "api.gleif.org",
      "method": "GET",
      "url": "https://api.gleif.org/api/v1/lei-records",
      "auth": "none"
    },
    {
      "step": 2,
      "source": "wikidata.org",
      "method": "GET",
      "url": "https://www.wikidata.org/w/api.php",
      "auth": "none"
    },
    {
      "step": 3,
      "source": "query.wikidata.org",
      "method": "GET",
      "url": "https://query.wikidata.org/sparql",
      "auth": "none"
    },
    {
      "step": 4,
      "source": "gleif.org",
      "method": "GET",
      "url": "https://api.gleif.org/api/v1/lei-records/{lei}/ultimate-parent",
      "auth": "none"
    },
    {
      "step": 5,
      "source": "gleif.org",
      "method": "GET",
      "url": "https://api.gleif.org/api/v1/lei-records/{lei}/direct-children",
      "auth": "none"
    },
    {
      "step": 6,
      "source": "api.gleif.org",
      "method": "GET",
      "url": "https://api.gleif.org/api/v1/lei-records/{lei}",
      "auth": "none"
    }
  ]
}

The saved catalog checks had expired at capture time. This recording includes a fresh client run; it does not update the catalog verification status.

Recorded from Atlas MCP and public sources on 2 Nov 2026. Inputs and results are shortened and normalized for readability. No live requests or account quota are used during replay.

01 · Atlas

The map and the recipe.

Atlas finds a chain, explains its inputs and returns the source endpoints and how they connect.

02 · Your tools

The requests and the result.

Your client runs the recipe. Data travels from the source to your tools, with source access under your control.

Try it with your own question.

Connect Atlas to your agent or use the REST API.

Connect Atlas
How do access and requests work?

Create an account and verify your email; administrator approval enables access. MCP and REST share your allowance. Search and planning use requests, while recipes and usage checks are free. This replay uses neither.