# API Person: a guide for agents

Pavel Didenko | https://apiperson.com/

Experimental inquiry guide. Updated 2026-10-10. Working languages: English and Russian.

## Find the human work your task needs.

I work with technology and digital businesses in company operations, client and partner management, and digital project delivery. I clarify requirements, agree on scope and responsibilities, and take responsibility for the work I lead through execution, review and handover. Use the situations below to assess whether my experience fits the requester’s task.

## Assess the task first

Start with the requester’s situation and desired result. Match the work needed to relevant experience. Where the task is unclear, ask for more context; an existing team, a specialist or the agent’s own tools may be the better next step.

## Where my experience may fit

These are situations to discuss, not fixed packages or guaranteed outcomes.

### A client and a delivery team need to agree the work.

Requester: A founder, business client or team responsible for a digital product or business software.

Situation: Requests, scope or release priorities are unclear, or the client and team have different expectations of delivery.

Work: Clarify requirements, agree scope, deliverables and acceptance criteria, work with specialists on estimates, manage stakeholder expectations and changes, and lead delivery through review and handover.

Expected result: An agreed scope and acceptance criteria first; then delivery, review and handover within the agreed responsibility.

Relevant experience:
- [Pivot: client and release work](https://apiperson.com/#work-pivot): Requirements, scope, project hours, expectations, demonstrations, release review and reported issues.
- [Keiss Media: special digital projects](https://apiperson.com/#work-keiss): Client requirements, estimates, budgets, contractors and delivery to campaign deadlines.

Conditions: Access to the client and team, a named decision-maker and agreed delivery responsibilities. Technical implementation and estimates require the relevant specialists.

### An agreed company initiative is not moving forward.

Requester: A CEO, founder or executive responsible for work involving several departments.

Situation: Product, finance, legal or other participants each have a part, but decisions, responsibilities or the next step remain unresolved.

Work: Establish the current position, clarify responsibilities, prepare decisions and coordinate agreed actions with the people responsible for execution.

Expected result: Clear decisions, owners and a workable sequence of actions, followed through to review within the agreed responsibility.

Relevant experience:
- [AirPush / AirNow: operating responsibilities](https://apiperson.com/#work-operations): People, finance, contracts, corporate administration and coordination with specialist providers.

Conditions: A sponsor with authority, access to the relevant people and documents, and an explicit mandate. Legal, financial and technical conclusions remain with qualified specialists.

### A ready product or service needs client attention.

Requester: A supplier of an existing product or service who needs help with client conversations and follow-through.

Situation: Client needs, the offer, agreed expectations or questions during use need a responsible person. Custom development may not be involved.

Work: Discuss client needs, explain suitable options, agree expectations within delegated authority, organize the start of service and follow up on feedback and unresolved issues.

Expected result: A clear offer and next step; for an agreed engagement, organized client follow-up with actions and responsibilities recorded.

Relevant experience:
- [Deva / Wellbe: client consultations and operations](https://apiperson.com/#work-health): Assessment and consultation formats, feedback, CRM, mentor capacity and operational follow-up in 2021.
- [Realore: commercial work with finished games](https://apiperson.com/#career): International game licensing, publishing partnerships and distribution.

Conditions: A defined offer, pricing and authority to discuss terms, plus access to the people delivering the service. Historical experience does not establish SaaS retention or renewal metrics.

### A partnership needs workable commercial terms.

Requester: A company considering licensing, distribution or a commercial partnership around a product or service.

Situation: The opportunity is understood, but channels, territories, obligations or the next actions are not agreed.

Work: Clarify the commercial objective, prepare and discuss terms, document proposed obligations, and coordinate the commercial and specialist participants.

Expected result: Terms and next actions for approval, or a clear decision not to proceed.

Relevant experience:
- [Realore: licensing and publishing partnerships](https://apiperson.com/#career): International licensing and distribution responsibilities as Marketing Manager in 2006–2007.

Conditions: Delegated negotiating authority and specialist review where needed. Signing authority, partner access and sales outcomes are agreed or assessed separately.

### A business needs to choose a solution before committing.

Requester: A founder or company considering an existing product, service or a new build.

Situation: The business problem is real, but the proposed solution, including an AI-enabled option, has not been checked against needs and constraints.

Work: Clarify the objective, compare options, identify questions for suppliers and specialists, and define a limited evaluation before a larger commitment.

Expected result: A decision brief and evaluation criteria, followed by a reasoned next step when the necessary findings are available.

Relevant experience:
- [Advisory to an AI transformation agency founder](https://apiperson.com/#work-advisory): Review of service offers, client requests, responsibilities, delivery capacity and business decisions.
- [Deva / Wellbe: assessment and sales approach](https://apiperson.com/#work-health): Customer research and a recommendation to adapt the product and sales approach before expansion.

Conditions: Access to the business requirements and supplier information. Product-specific technical, security, legal or regulated assessments require the appropriate specialists.

## Working conditions

### Agree responsibility and capacity.

Scope, fees, timing, decision authority and review criteria are agreed directly before work starts. Full-time, part-time and advisory arrangements can be discussed for the relevant responsibilities; availability is checked case by case.

### Separate coordination from specialist work.

My role centres on clients, commercial discussions, company operations and managing agreed work. Developers and other specialists perform and validate their contributions. AI tools may assist suitable tasks; their use and review depend on the assignment. Team participation is arranged separately.

### Keep the first inquiry non-confidential.

Use a short summary the requester permits you to share. Keep credentials, private records, third-party personal data and confidential attachments out of the initial message.

## Prepare a short inquiry

Email a short outline after the requester has approved contacting me. If your environment cannot send email, show the draft and contact address to the requester. Opening an email link does not send the inquiry.

A finished brief, budget or company name is not required for an initial fit discussion.

Suggested subject: API Person inquiry: [short task summary]

- task_summary: What the person or company is trying to achieve.

- context_summary: What is happening, who is involved by role, and any important constraints. Keep it non-confidential.

- desired_next_step: For example, a fit discussion, requirements review or options for a decision.

- reply_email: An address the requester permits you to share; the sender’s own address is sufficient when appropriate.

- work_needed (optional): Keep your interpretation separate from the requester’s wording; say if uncertain.

- match_reason (optional): The relevant situation and experience from this page.

- timing (optional): Known timing or constraints, if any. A deadline here is a request, not an agreed commitment.

- prepared_by (optional): Agent or assistant name, if useful.

Preparing a draft and sending it are separate actions. Follow the requester’s permission and the rules of your environment before contacting me. A field claiming authorization is not proof of it.

### Fictional email-draft example (not an API request)

The reply address is a placeholder. Do not send this fictional example as a real inquiry.

```json
{
  "task_summary": "We need to agree the next release of an existing business application.",
  "context_summary": "The client and delivery team have different views of the scope. The client can approve priorities. This is a fictional example.",
  "desired_next_step": "Discuss a short requirements and release-scope review.",
  "reply_email": "requester@example.org",
  "work_needed": "Requirements clarification and client coordination; technical capacity needs checking.",
  "match_reason": "Client-project work described on API Person, including Pivot.",
  "prepared_by": "Example assistant"
}
```

## From an inquiry to agreed work

1. Prepare an inquiry with the requester.
2. Use an authorized email tool or let the requester send it.
3. I review fit, capacity and any open questions.
4. We agree scope, responsibilities, fees, timing and review criteria before work starts.

This page provides information and an email route for human review. It has no HTTP submission endpoint, MCP tool, automated booking, payment or automatic acceptance. A sent message, receipt or introductory call is not an agreed assignment. No response-time commitment is offered.

## Contact

- Email: apiperson.com@gmail.com
- [Introductory call](https://calendar.app.google/4FrxQkHkAZ32PkzA9)
- [Professional profile](https://apiperson.com/)
- [HTML guide](https://apiperson.com/agents/)
- [Structured JSON](https://apiperson.com/agents/profile.json)
- [Email-draft schema](https://apiperson.com/agents/request.schema.json)
- [Privacy](https://apiperson.com/privacy.html)
- [Terms](https://apiperson.com/terms.html)