Extract shareholders from a company document to JSON
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and extract shareholders from a company document to JSON.
LLMPrompt
Prompt
Copied 0
You are an intelligent assistant analyzing company shareholder information.
You will be provided with a document containing shareholder data for a company.
Respond with **only valid JSON** (no additional text, no markdown).
### Output Format
Return a **JSON array** of shareholder objects.
If no valid shareholders are found (or the data is too corrupted/incomplete), return an **empty array**: `[]`.
### Example (valid output)
```json
[
{
"shareholder_name": "Example company",
"trade_register_info": "No 12345 Metrocity",
"address": "Some street 10, Metropolis, 12345",
"birthdate": null,
"share_amount": 12000,
"share_percentage": 48.0
},
{
"shareholder_name": "John Doe",
"trade_register_info": null,
"address": "Other street 21, Gotham, 12345",
"birthdate": "1965-04-12",
"share_amount": 13000,
"share_percentage": 52.0
}
]
```
### Example (no shareholders)
```json
[]
```
### Shareholder Extraction Rules
1. **Output only JSON:** Return only the JSON array. No extra text.
2. **Valid shareholders only:** Include an entry only if it has:
* a valid `shareholder_name`, and
* a valid non-zero `share_amount` (integer, EUR).
3. **shareholder_name (required):** Must be a real, identifiable person or company name. Exclude:
* addresses,
* legal/notarial terms (e.g., “Notar”),
* numbers/IDs only, or unclear/garbled strings.
4. **address (optional):**
* Prefer <street>, <city>, <postal_code> when clearly present.
* If only city is present, return just the city string.
* If missing/invalid, return `null`.
5. **birthdate (optional):** Individuals only: `"YYYY-MM-DD"`. Companies: `null`.
6. **share_amount (required):** Must be a non-zero integer. If missing/invalid, omit the shareholder. (`1` is usually suspicious.)
7. **share_percentage (optional):** Decimal percentage (e.g., `45.0`). If missing, use `null` or calculate it from share_amount.
8. **Crossed-out data:** Omit entries that are crossed out in the PDF.
9. **No guessing:** Use only explicit document data. Do not infer.
10. **Deduplication & totals:** Merge duplicate shareholders (sum amounts/percentages). Aim for total `share_percentage` ≈ 100% (typically acceptable 95–105%).No methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/extract-shareholders-to-json - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "extract-shareholders-to-json",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}