निजी कंपनी की समुचित जाँच

---
name: akta-private-company-due-diligence
description: Build a structured private-company diligence packet that separates reviewed Akta data, bounded public evidence, risks, unknowns, and credit use.
---

# Private Company Due Diligence

## Loadout capabilities

Use <action-tag>api:akta_api:company_search</action-tag> to resolve the entity. Use <action-tag>api:akta_api:company_enrichment</action-tag> for approved profile sections, <action-tag>api:akta_api:company_metrics_fixed</action-tag> for the fixed company metrics view, <action-tag>api:akta_api:reviews_variable</action-tag> for explicitly selected review sources and fields, and the News operation from <integration-tag>api:akta_api</integration-tag> for a bounded news window. For diligence questions that require independent public evidence, use the Exa Search Action from <integration-tag>composio:exa_tools</integration-tag> to identify relevant primary sources and <action-tag>api:tinyfish_api:fetch_urls</action-tag> to extract the reviewed pages.

## Outcome

Create a reviewable diligence packet for a screening decision. This is a research aid, not legal, accounting, security, investment, or regulatory diligence, and it must not turn missing data into a favorable conclusion.

## Required inputs

- Target company name and official domain when known.
- Decision, diligence questions, and material risk themes.
- Required enrichment, metric, review, and news fields.
- Date windows, permitted public-source scope, and maximum approved Loadout credit spend.

## Workflow

1. Convert the decision into a short evidence checklist. Mark each item required, optional, or unavailable through Akta.
2. Resolve the company and confirm its official domain and Akta identity. Stop when identity evidence conflicts.
3. Preflight the minimal enrichment and variable review requests. Combine those quotes with fixed-price metric and bounded news requests, then show the total before execution.
4. Execute only the approved Akta requests. Preserve returned source context and dates, and keep reviews or third-party claims attributed.
5. For checklist items that Akta does not cover or that need corroboration, run bounded Exa searches, review the results, and fetch only selected primary-source URLs with Tinyfish. Never use public search to fill a structured field silently.
6. Build an evidence matrix with `supported`, `contradicted`, `unresolved`, or `not covered` for each diligence question. Summarize material risks without converting correlations into facts.

## Output contract

- `Entity`: reviewed identity and match evidence.
- `Evidence matrix`: diligence question, status, fact, source type, URL or Akta context, date, and limitation.
- `Company profile and metrics`: requested fields only.
- `Reviews and news`: attributed observations with bounded periods.
- `Risks and follow-ups`: evidence-backed concerns plus external diligence still required.
- `Unknowns and cost`: missing evidence, quotes, actual credits, and Actions called.

## Failure and recovery

- Do not run priced reads against an ambiguous entity; present candidates for confirmation.
- If the total quote exceeds the budget, rank fields by decision value and ask which to remove.
- If metrics or reviews conflict, show both with dates and sources; do not average them into certainty.
- If data is unavailable, mark the question unresolved and recommend an appropriate primary-source check.
- If a public source conflicts with Akta, preserve both observations and lower confidence instead of choosing the favorable result.