Integration
Connect 3Scribe to Crossref Metadata Search
When something happens in 3Scribe, your agent does the next thing in Crossref Metadata Search. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want 3Scribe and Crossref Metadata Search to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with 3Scribe and Crossref Metadata Search
Triggers and actions 1 trigger ยท 9 actions
Trigger
Job CompleteTriggers when a transcription job has completed.
- Create Transcription Job
Posts a file to 3Scribe to be transcribed
- Delete Transcription Job
Delete a specified transcription job from 3Scribe, permanently removing all files and transcripts. Endpoint: DELETE https://api.3scri.be/jobs/:jobid (header APIKey required). Path parameter: jobid (string). Returns 200 on success.
- Fetch Transcript
Fetches a specific jobs transcript
Action
Find funders by querySearch the Crossref Funder Registry for funding organizations matching a free-text query. GET /funders
- Find works by query
Search Crossref's bibliographic metadata for works (articles, books, conference papers, etc.) matching a free-text query, with optional filters and sorting. GET /works
- Get funder
Retrieve metadata for a funding organization and its suborganizations by funder ID. GET /funders/{funder_id}
- Get journal
Retrieve information about a journal by its ISSN. GET /journals/{issn}
- Get member
Retrieve metadata for a Crossref member (publisher) by member ID. GET /members/{member_id}
- Get work by DOI
Retrieve full Crossref metadata for a single work given its DOI. GET /works/{doi}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.