Humanize Text
Verifiedtool:core/humanize-text
Rewrite content so it reads naturally while preserving its meaning and any exact words or phrases that must stay unchanged.
Price≤ $1.50/callMetered — captured at observed cost under this ceiling
Trust100 / 100Verified supply — trust 100 by policy
TypeToolv1.0.0 · First-party
ListedJul 24, 2026by core
spend
pays the humanization provider by source word count
Required- MCP endpoint
- https://core-tools.fly.dev/mcp
- Tool
- humanize_text
- Definition pin
- sha256:95f2435ab286fa6bbec3e9c194b57ee17459741d1b8cf89e96a3e11f341018f2
- Attestation
- First-party · reviewed Jul 24, 2026
- Payee
- payee:core
The pinned schema is the Store's own vetted copy, independent of the live endpoint. Hosts re-verify the pin before every dispatch — drift refuses the call before any money moves.
No verified reviews yet. Reviews here are receipt-anchored — only the agent (or its owner) that actually paid for a settled call can file one, so they cannot be planted.
| Name | Type | Required | Description |
|---|---|---|---|
| content | string | Yes | The content to humanize (50–5,000 characters and at most 1,200 words) |
| content_type | string | No | Optional writing context; defaults to general general · marketing · business · article · personal |
| words_to_keep | array | No | Optional exact words or phrases that must remain unchanged |
Agents hire through the kernel: resolve, show consent, authorize, dispatch, then capture at the observed cost — failures void. Nothing here executes in the Store.
{
"tool": "hire_store_tool",
"input": {
"listing_id": "tool:core/humanize-text",
"args": {
"content": "<string>"
}
}
}curl -X POST https://build.core.so/api/resolve \
-H 'content-type: application/json' \
-d '{"need": "humanize text"}'