From 07eeff4e94aa11f5094cdb7997f907968e86d911 Mon Sep 17 00:00:00 2001
From: Alex Potsides <alex@achingbrain.net>
Date: Sat, 5 Aug 2023 18:20:08 +0100
Subject: [PATCH] docs: update readme with api info (#11)

Updates the readme to link to the ipni spec and also http routing v1.

Fixes #3

---------

Co-authored-by: Steve Loeppky <stvn@loeppky.com>
---
 README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/README.md b/README.md
index 4fc2dc5..836d00a 100644
--- a/README.md
+++ b/README.md
@@ -9,6 +9,7 @@
 
 ## Table of contents <!-- omit in toc -->
 
+- [About](#about)
 - [Install](#install)
   - [Browser `<script>` tag](#browser-script-tag)
 - [Example](#example)
@@ -16,6 +17,12 @@
 - [License](#license)
 - [Contribution](#contribution)
 
+## About
+
+This is an implementation of the libp2p [content routing interface](https://libp2p.github.io/js-libp2p-interfaces/interfaces/_libp2p_interface_content_routing.ContentRouting.html) that uses an [IPNI](https://github.com/ipni/specs) HTTP endpoint.
+
+An alternative is [HTTP Routing V1](https://github.com/libp2p/js-reframe-content-routing) (previously known as Reframe) but the advantage of IPNI at least as of 2023-05-19 is that it returns results in a streaming fashion which can be faster.  Note that this will change with the rollout of [IPIP-410](https://github.com/ipfs/specs/pull/410), at which point one can use the HTTP Routing V1 interface/implementation directly.
+
 ## Install
 
 ```console