[Integrations](https://spiral.ai/integrations) › [Amp](https://spiral.ai/integrations/amp) › [DOI prefix lookup](https://spiral.ai/integrations/amp/doi-prefix-lookup)

# How to Use DOI prefix lookup in Amp

Inspect the agency and metadata routing information associated with a DOI prefix. Use it to understand shared routing before processing DOI records under that prefix.

|  |  |
| --- | --- |
| Model | DOI prefix lookup |
| Available through | Alexandria |
| Category | Developer |
| Price | $0.00873 per call. |
| Returns | json |
| Runs | In the background |
| Setup | About 2 minutes, no API key |

## Prompts to try with DOI prefix lookup in Amp

- Use DOI prefix lookup to look this up and give me the result as a table. Save the result in ./assets.
- Pull the latest numbers from DOI prefix lookup and tell me what changed since last week.
- Check DOI prefix lookup and summarize what you find in three bullet points.
- Pull the newest data from DOI prefix lookup and give me the result as a table.
- Check DOI prefix lookup every morning and tell me only when something changed.

## How to set up DOI prefix lookup in Amp

Pick the way that suits you. Each takes about two minutes.

### Use Spiral's MCP server

1. **Add the server**: No header and no client ID or secret: Amp registers itself with Spiral.

```bash
amp mcp add spiral https://api.spiral.ai/mcp
```

2. **Sign in**: Start `amp`. Amp opens Spiral's sign-in page in your browser: sign in, pick the organization and click Authorize. No API key.

3. **Check it**

```bash
amp mcp doctor
```

### Use the Spiral skill

1. **Send Amp this message**: Your agent reads Spiral's skill and sets itself up.

```
set up https://spiral.ai/SKILL.md
```

2. **Sign in or paste a key**: Approve Spiral in the browser, or give the agent a key from the console.

### Use the Spiral CLI

1. **Install and sign in**: Installs the Spiral CLI, signs you in and adds its skill to your coding agents.

```bash
npx -y spiral-cli@latest init
```

### Call the Spiral API

1. **Create an API key**: In the console, under API keys.

2. **Run DOI prefix lookup**: One request; the result comes back by polling or a webhook.

```bash
curl https://api.spiral.ai/v1/runs \
  -H "Authorization: Bearer $SPIRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "provider": "alexandria",
    "model": "doi-org/identifiers/prefix",
    "input": {
      "prefix": "<prefix>"
    }
  }'
```

Then paste one of the prompts above: Amp finds DOI prefix lookup on Spiral, shows the price and runs it.

Setup guide in the docs: https://spiral.ai/docs/quickstarts/amp

## DOI prefix lookup tools and prices

- [DOI.org · Prefix](https://spiral.ai/tools/alexandria/doi-org/identifiers/prefix) (Alexandria): $0.00873 per call.

## What can you do with DOI prefix lookup in Amp?

Build a DOI report with citations, registered destinations, agency routing, and system activity. Coding agents can turn returned records into project fixtures, comparison views, and checks for a bibliography import.

### Audit DOI ingestion

Check incoming identifiers, identify their agencies, inspect prefix routing, and compare returned metadata with the catalog records being imported.

### Review a publisher migration

Compare registered destinations and citation records before and after a platform move. Inspect agency and prefix routing when records behave differently.

### Plan a DOI reporting application

Use public DOI examples to design citation, destination, and agency views. Add system statistics and the agency directory to provide context for the application’s reports.

### Teach library staff how DOI records work

Walk through a public DOI’s citation, destination, agency, and prefix routing. Use the directory and resolution statistics to explain the wider DOI system.

## Overview

- [Alexandria](https://spiral.ai/providers/alexandria)
- [All Amp guides](https://spiral.ai/integrations/amp)

## DOI prefix lookup in other agents

- [ChatGPT](https://spiral.ai/integrations/chatgpt/doi-prefix-lookup)
- [Claude](https://spiral.ai/integrations/claude-desktop/doi-prefix-lookup)
- [Claude Code](https://spiral.ai/integrations/claude-code/doi-prefix-lookup)
- [Cline](https://spiral.ai/integrations/cline/doi-prefix-lookup)
- [Codex](https://spiral.ai/integrations/codex/doi-prefix-lookup)
- [Cursor](https://spiral.ai/integrations/cursor/doi-prefix-lookup)
- [Devin](https://spiral.ai/integrations/devin/doi-prefix-lookup)
- [dots](https://spiral.ai/integrations/dots/doi-prefix-lookup)
- [Factory Droid](https://spiral.ai/integrations/factory-droid/doi-prefix-lookup)
- [Gemini](https://spiral.ai/integrations/gemini/doi-prefix-lookup)
- [Gemini CLI](https://spiral.ai/integrations/gemini-cli/doi-prefix-lookup)
- [Google Antigravity](https://spiral.ai/integrations/antigravity/doi-prefix-lookup)
- [goose](https://spiral.ai/integrations/goose/doi-prefix-lookup)
- [Grok](https://spiral.ai/integrations/grok/doi-prefix-lookup)
- [Grok Build](https://spiral.ai/integrations/grok-build/doi-prefix-lookup)
- [Hermes](https://spiral.ai/integrations/hermes/doi-prefix-lookup)
- [Instinct](https://spiral.ai/integrations/instinct/doi-prefix-lookup)
- [Manus](https://spiral.ai/integrations/manus/doi-prefix-lookup)
- [Muse](https://spiral.ai/integrations/muse/doi-prefix-lookup)
- [Muse Code](https://spiral.ai/integrations/muse-code/doi-prefix-lookup)
- [n8n](https://spiral.ai/integrations/n8n/doi-prefix-lookup)
- [Notion](https://spiral.ai/integrations/notion/doi-prefix-lookup)
- [OpenClaw](https://spiral.ai/integrations/openclaw/doi-prefix-lookup)
- [opencode](https://spiral.ai/integrations/opencode/doi-prefix-lookup)
- [Perplexity](https://spiral.ai/integrations/perplexity/doi-prefix-lookup)
- [Raycast](https://spiral.ai/integrations/raycast/doi-prefix-lookup)
- [VS Code](https://spiral.ai/integrations/vscode/doi-prefix-lookup)
- [Windsurf](https://spiral.ai/integrations/windsurf/doi-prefix-lookup)
- [Zapier](https://spiral.ai/integrations/zapier/doi-prefix-lookup)

## More Amp guides

- [DOI monthly statistics](https://spiral.ai/integrations/amp/doi-monthly-statistics)
- [DOI registration agency directory](https://spiral.ai/integrations/amp/doi-registration-agency-directory)
- [DOI landing page lookup](https://spiral.ai/integrations/amp/doi-landing-page-lookup)
- [DOI registration agency lookup](https://spiral.ai/integrations/amp/doi-registration-agency-lookup)
- [DOI citation metadata](https://spiral.ai/integrations/amp/doi-citation-metadata)
- [DOI resolution statistics](https://spiral.ai/integrations/amp/doi-resolution-statistics)

## Questions about DOI prefix lookup in Amp

**Can Amp use DOI prefix lookup?**

Yes. Add Spiral to Amp as an MCP server, and Amp can find and run DOI prefix lookup like any built-in tool.

**How much does DOI prefix lookup cost in Amp?**

$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Amp plan is separate.

**Do I need an Alexandria account to use DOI prefix lookup in Amp?**

No. Spiral runs DOI prefix lookup on its own Alexandria account. You sign in to Spiral once and never paste a key.

**How long does it take to set up DOI prefix lookup in Amp?**

About two minutes: add the server, then sign in, then check it.

**Does Amp wait while DOI prefix lookup runs?**

DOI prefix lookup runs in the background. Amp starts the run, checks on it and gives you the json when it's ready.

**Does DOI coverage stop at journal articles?**

No. DOI registration agencies also serve entertainment, standards, construction products, natural history collections, and research data.

**How quickly do changed DOI destinations appear?**

DOI.org documents a 24-hour cache for Handle values. A destination change can therefore take up to 24 hours to appear through the proxy.

**Can citation metadata be retrieved as one large batch?**

DOI content negotiation returns one metadata record at a time. The underlying agency lookup supports multiple DOIs, but that does not make citation retrieval a batch service.

**Does a DOI prefix prove who owns a work?**

No. The DOI Handbook explicitly says a registrant code does not establish ownership of rights or current management responsibility.

**Does converted citation metadata preserve every source distinction?**

No. Crossref documents mappings where several source types become one output type, so converted records can lose distinctions present in the original agency schema.

