0.25¢ per URL

Let Codexread the page.

A task that needs to know what a page is should not have to grow a parser. Title, description, social image, canonical and favicon, a quarter of a cent a call.

TaskFuel connects Codex to paid tools through one prepaid balance. You review the provider and request quote before spending.

Works with

What your agent can call.

Currently available through 2s. Your AI picks the one that fits and checks the exact price before it pays.

  • Extract URL metadata

    Extract a public page’s metadata, including its title, canonical URL and social image. Only fields present in the fetched page can be returned.

    0.25¢

Try it in your next task.

Sign in to TaskFuel and copy the connection prompt into your agent. Approve the connection, then ask for the work you need.

Connect the environment running your Codex task. Give Codex the target file path or response format so the paid result can be used in the same task.

01

Name the task

Tell your agent what the output needs to contain.

02

See the price

Ask for the provider and request quote before spending.

03

Review the response

Check the output against your task. The call reports its cost and remaining balance.

When to use it.

Link previews

Skip the Open Graph parser.

Codex can build the feature around structured fields instead of writing and then maintaining the extraction itself.

Auditing routes

Find pages that unfurl badly.

Run the sitemap through it and see which routes are missing a description or a social image. A hundred URLs is about a quarter.

Validating input

Confirm a URL before storing it.

When users submit links, one call tells you what is actually there before it goes in the database.

Providers for this task.

CapabilityProvidersReference
Preview a link2sCompare routes · Endpoint data

Good Questions.

What does a Codex task get back?

The page title, description, social image, canonical URL, favicon, author and other structured metadata, as one quoted call.

What does it cost?

0.25¢ per URL. Auditing a hundred routes costs about a quarter.

Why not fetch and parse it in code?

You can, and then the task owns the redirects, the malformed tags and the pages that need JavaScript. This returns the fields already extracted.

Do I need a scraper account?

No. One TaskFuel account and one prepaid balance covers it.

What if a URL fails?

Upstream 4xx and 5xx responses are not charged. A successful provider response can still be charged when its answer is empty or unhelpful.

Your agent can do things it couldn’t this morning.

$1 in free credit, no card required.

Start for Free