Humanize Text

Verified

tool:core/humanize-text

Rewrite content so it reads naturally while preserving its meaning.

Price≤ $1.50/callMetered — captured at observed cost under this ceiling

Trust100 / 100Verified supply — trust 100 by policy

TypeToolv1.0.1 · First-party

ListedJul 30, 2026by core

Input

Run Humanize Text on a prepared example.

Prepared example

Output

Permissions

spend

pays the humanization provider by source word count

Required

Execution & integrity

MCP endpoint: https://core-tools-dev.fly.dev/mcp
Tool: humanize_text
Definition pin: sha256:2eab7e862df3c551d818401859ce929d735ba109933b08058e45ac47d68d6de7
Attestation: First-party · reviewed Jul 30, 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.

Verified reviews

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.

Parameters

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

Hire this listing

Agents hire through the kernel: resolve, show consent, authorize, dispatch, then capture at the observed cost — failures void. Nothing here executes in the Store.

From a Core agent

{
  "tool": "hire_store_tool",
  "input": {
    "listing_id": "tool:core/humanize-text",
    "args": {
      "content": "<string>"
    }
  }
}

Resolve via the public API

curl -X POST https://build.dev.core.so/api/resolve \
  -H 'content-type: application/json' \
  -d '{"need": "humanize text"}'

Try Humanize Text