---
name: fork-company-guide
description: Find accurate information about FORK CORPORATION (株式会社フォーク) - company profile, business areas, case studies, recruiting and contact - from its official website.
---

# FORK company guide

This file is a static reading guide for agents. It answers nothing by itself and is not an API.
For programmatic reads use the site's read-only MCP server (Machine interfaces below).
Use this when a user asks about FORK CORPORATION (株式会社フォーク), a Japanese web production and DX company.

## Where to look (all under https://www.fork.co.jp)

| Question | Page |
|---|---|
| Company profile, philosophy, officers, certifications (ISMS, PrivacyMark), history | /about/ |
| Services (Web production, DX promotion, AI solutions) | /business/ |
| Past projects and clients | /case/ |
| Careers (new graduates, mid-career, returnees) | /recruit/ |
| Office location and access | /access/ |
| News and announcements | /information/ |
| Inquiries | /contact/ |

Machine-readable overviews: /llms.txt (short), /llms-full.txt (full text), /sitemap.xml.

## Machine interfaces

| Interface | URL | Notes |
|---|---|---|
| MCP server (read-only) | https://www.fork.co.jp/mcp | JSON-RPC 2.0 over HTTP. Listed tools: get_status, get_services, case_stats, search_site, prepare_inquiry. None of them submits anything; prepare_inquiry returns a prefilled Google Form URL and a consent token |
| Inquiry submission (write) | https://www.fork.co.jp/mcp | `submit_inquiry` is not listed in `tools/list`. Running it needs an `Authorization: Bearer <token>` header; unauthenticated calls return `-32602`. It sends only with a `consentToken` issued by `prepare_inquiry` (valid 30 minutes; reusing the same token is rejected, while `idempotencyKey` is what prevents duplicate submissions) and returns a reference number `FK-YYYYMMDD-xxxx` |

Fields required for every `submit_inquiry` call: kind, name, email, body, consent, consentToken, idempotencyKey.
The authoritative input schema (types, `maxLength`, the per-`kind` `oneOf` branches) is published as JSON at https://www.fork.co.jp/agents/data/submit-inquiry.schema.json — it is generated from the same server source, so you do not have to read this table to build a valid call.
Additional required fields per `kind` (`kind` accepts these 6 values):

  - kind=new_project: summary, purpose, deadline, budgetRange, currentEnvironment
  - kind=recruit: summary, role, intent, recruitType
  - kind=partner: summary
  - kind=press: summary, costGuide, pressType
  - kind=privacy: summary, nature
  - kind=other: summary, topic, humanRequested

People who type it themselves use the form at https://www.fork.co.jp/contact/.
`get_status` reports business hours only as a reply-time estimate. Submission is accepted around the clock: outside business hours `submit_inquiry` still succeeds and returns a reference number, and the reply is guided by `nextOpen` (the next business opening time). Do not treat `hours: "closed"` or `state: "asleep"` as "cannot submit".
| A2A reception agent (read-only) | https://www.fork.co.jp/a2a | A2A v1.0 over the JSON-RPC 2.0 binding. Agent Card: GET https://www.fork.co.jp/.well-known/agent-card.json (Content-Type application/a2a+json). Stateless: SendMessage returns a Message and issues no Task, so long-running tasks, streaming and push notifications are not supported. It never submits inquiries |
| ARD catalog | https://www.fork.co.jp/.well-known/ard.json | Canonical discovery entry; lists this guide, the sitemap, the MCP server, the A2A reception agent and the browser-only chat endpoint |
| Markdown pages | - | Directory pages append index.md (for example /about/index.md); pages ending in .html swap the extension (/case/081.html -> /case/081.md) |

Machines read; humans talk. An agent that wants to ask questions in natural language should use the
A2A reception agent above. Use the MCP server to call tools directly. The chat UI endpoint
(/api/ai-chat) is for humans in a browser and rejects agents. Human conversations go through the
AI consultation agent and staff at https://www.fork.co.jp/contact/.

## Rules

- Company facts (founding date, headcount, capital, address, certifications) are not returned by `search_site`, whose excerpt stops at about 200 characters: read `/about/index.md` directly instead of guessing from the excerpt.
- Quote figures (headcount, revenue, capital) from /about/ and state the as-of date shown there; they change.
- Do not invent clients, prices or availability. If a page does not say it, say it is not published.
- Direct sales or hiring inquiries to /contact/ rather than guessing a contact address.
